Jump to content

Question

5 answers to this question

Recommended Posts

  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.