Anisotropic Defixation
New member
- Messages
- 122
- Points
- 0
Is there a better way to debug?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
When GDB fails
- Thread starter Anisotropic Defixation
- Start date
Anisotropic Defixation
New member
- Messages
- 122
- Points
- 0
Oh I mean that it doesn't report anything at all since the issue seems to be deep one.
Dastgir
Core Developer
- Messages
- 3,805
- Points
- 0
- Discord
- Dastgir#1460
- IRC Nickname
- Dastgir
- Github
- dastgirp
- Emulator
- Client Version
- 2019-02-28 RE
AFAIK, gdb is the best way.
Why don't you post the coredump here and we may help you find the issue?
Gdb always gave me the correct info, no matter how much deep is the issue.
Why don't you post the coredump here and we may help you find the issue?
Gdb always gave me the correct info, no matter how much deep is the issue.
Anisotropic Defixation
New member
- Messages
- 122
- Points
- 0
Issue is there's no dump, the crash isn't even detected and recorded, map server just dies while console happily continues to go on, saving things without even reporting it.
Last edited by a moderator:
- Messages
- 1,191
- Points
- 83
- Discord
- 4144
- IRC Nickname
- _41444d494e_
- Github
- 4144
- Emulator
- Client Version
- latest
Gdb cant not detect crash.
It can be not crash but emergncy termination. This can happend if by some reason server want to terminate self. For detect this need know where and why server may exit.
Also for better detecting memory corruption or other execution issue possible to use santity flags. They partially can work in gcc 4.9 and better works in gcc 5.
Server will works bit slower. It will report not critial issues to console and will terminate with full issue description if critical issue happend.
For this server can be compiled like this:
It can be not crash but emergncy termination. This can happend if by some reason server want to terminate self. For detect this need know where and why server may exit.
Also for better detecting memory corruption or other execution issue possible to use santity flags. They partially can work in gcc 4.9 and better works in gcc 5.
Server will works bit slower. It will report not critial issues to console and will terminate with full issue description if critical issue happend.
For this server can be compiled like this:
Code:
make clean./configure --enable-manager=no --enable-sanitize=full --disable-lto --enable-debug=gdbmake