For that
purpose there is a NDEBUG deffinition used all over the
sources.
Hmm, it starts to get complicated :)
And if I want to backtrace handler, but I do not want NDEBUG
because it
enables additional debugging code, that I not want in this
situation?
You two are now discussing things over my head! :-)
Slavek, I basically copied your original patch and modified as
necessary. You do what else is necessary to satisfy yourself and
everybody else.
That said, the next official version of Slackware will include
demangle.h in binutils, although I know some other distros still do
not. I am now rebuilding binutils that came with Slackware 14.0 so
I can have demangle.h and creae useful backtraces. The tdelibs
configuration patch is still needed, of course, for those distros
that don't.
Should the default be ON or OFF? I don't know. Seems we need the
backtrace abilities only for debugging. So while we debug bug
report 1627, having the backtrace is nice. Once Tim resolves the
cause is the backtrace ability necessary thereafter? Probably not
unless we again run into the same problem with a different cause.
If the default is OFF then the developer support request in the bug
report will be "Please rebuild tdelibs with -
DWITH_TDEIOSLAVE_BACKTRACE=ON."
Just my two cents. :-)
Darrell
