Anisotropic Defixation 18 Posted May 28, 2015 Is there a better way to debug? Quote Share this post Link to post Share on other sites
0 Dastgir 1244 Posted May 28, 2015 How come gdb fails? Start with gdb map-serverrun Quote Share this post Link to post Share on other sites
0 Anisotropic Defixation 18 Posted May 28, 2015 Oh I mean that it doesn't report anything at all since the issue seems to be deep one. Quote Share this post Link to post Share on other sites
0 Dastgir 1244 Posted May 28, 2015 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. Quote Share this post Link to post Share on other sites
0 Anisotropic Defixation 18 Posted May 28, 2015 (edited) 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. Edited May 28, 2015 by Anisotropic Defixation Quote Share this post Link to post Share on other sites
0 4144 364 Posted June 3, 2015 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: make clean./configure --enable-manager=no --enable-sanitize=full --disable-lto --enable-debug=gdbmake Quote Share this post Link to post Share on other sites
Is there a better way to debug?
Share this post
Link to post
Share on other sites