By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1710 - Improve handling of NDEBUG and backtrace support
Summary: Improve handling of NDEBUG and backtrace support
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-11-12 17:11 CST by Darrell
Modified: 2018-05-27 10:49 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-11-12 17:11:43 CST 
This concern was discussed in bug 1627 comment 19.

Currently a kcrash backtrace is seen only when hacking files to #undef NDEBUG. This should be changed such that that kcrash backtraces are enabled at all times.
Comment 1 Michele Calgaro 2013-11-24 01:56:38 CST 
As part of addressing this bug, fprintf debug messages should be converted to kdDebug messages
Comment 2 Darrell 2013-11-24 11:56:32 CST 
>As part of addressing this bug, fprintf debug messages should be converted to
>kdDebug messages
At the least, those fprintf messages qualified by #ifndef NDEBUG. :-)

Another note: many kdDebug() messages should be converted to kdDebug(xxxx) to facilitate toggling through kdedebugdialog. More than likely this will mean adding some new kdDebug categories.