Archived

This topic is now archived and is closed to further replies.

Mystery

[2016-01-10] Enable debug information in configure by default

Recommended Posts

Rationale:
Historically, we've received several crash reports or null pointer reports that were of barely any use, because they were produced by servers built without debug information.

Contents:
The default build mode, when using the UNIX ./configure && make build scripts, is now set to include debug information.

Impact:
The performance decrease when built in debug mode should be negligible. In any case, it's still possible to disable the debug mode while compiling.
Users concerned with minimal performance improvements, who don't want a readable backtrace in case of issues, can still pass --disable-debug to the configure script.

Details:
The configure script provides a command line flag to enable/disable/configure the debug mode options:

Before this commit, the default, when passing no options, was equivalent to:

./configure --disable-debug

After this commit, the default will be:

./configure --enable-debug

Another recommended option worth mentioning, that might improve the debugger's ability to produce meaningful information (in case of gdb) is:

./configure --enable-debug=gdb

Merge Date:
Sun, 10 Jan 2016 18:34:56 +0300

Related Pull Requests:
- #1090 - https://github.com/HerculesWS/Hercules/pull/1090 - Enable debug information in configure by default. [Andrei Karas]

Related Commits:
- d0af903 - https://github.com/HerculesWS/Hercules/commit/d0af903 - Sun, 10 Jan 2016 18:34:56 +0300 Enable debug information in configure by default. [Andrei Karas]
- c01f745 - https://github.com/HerculesWS/Hercules/commit/c01f745 - Sun, 10 Jan 2016 18:41:19 +0100 Merge pull request #1090 from 4144/enabledebug [Haru]

View the full article

Share this post


Link to post
Share on other sites