16 Aug
2013
16 Aug
'13
12:34 a.m.
2013/8/16 Slávek Banko <slavek.banko(a)axis.cz>
On Friday 16 of August 2013 02:22:50 Fat-Zer wrote:
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?
Slavek
--
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
For now there is only one call to backtrace_symbols and it's already
protected by NDEBUG ifdef.
2013/8/16 Slávek Banko
<slavek.banko(a)axis.cz>
> On Friday 16 of August 2013 02:16:40 Fat-Zer wrote:
> > 2013/8/16 Slávek Banko <slavek.banko(a)axis.cz>
> >
> > > On Friday 16 of August 2013 01:56:03 Timothy Pearson wrote:
> > > > > On Friday 16 of August 2013 00:39:24 Darrell Anderson wrote:
> > > > >> /dev/shm/tdelibs/tdeio/tdeio/backtrace_symbols.c:57:22:
fatal
> > > > >> error: demangle.h: No such file or directory
> > > > >>
> > > > >> We ran into this before with tdebase and we added
> > > > >> DWITH_KDESKTOP_LOCK_BACKTRACE as a configure option in
commit
> > > > >> 936d3cec 2013-01-26.
> > > > >>
> > > > >> demangle.h is not supported in all distros.
> > > > >>
> > > > >> I'll try to massage 936d3cec into tdelibs.
> > > > >>
> > > > >> Darrell
> > > > >
> > > > > As soon as I saw Tim's commit, it was clear to me that we
will
> > > > > need to add such a choice. You have prepared a patch or should
I
> > > > > do it?
> > > > >
> > > > > Slavek
> > > > > --
> > > >
> > > > Sorry about that guys, I only had a short time to work on the
crash
>
> bug
>
> > > > and therefore didn't add in the compile time checks/flags.
Thanks
>
> for
>
> > > > cleaning this up!
> > > >
> > > > Tim
> > >
> > > Two questions:
> > > 1) backtrace handler we want by default ${WITH_ALL_OPTIONS} or OFF?
> > > 2) and for Debian/Ubuntu packages by default ON or OFF?
> > >
> > > Slavek
> >
> > Wait a minute, don't apply it... IMO, it place there the system
> > configuration check fits better than prompting another option. Isn't
> > it?
>
> Not exactly - even if the system is suitable for backtrace handler may
be
deliberately specified building without backtrace handler.
Slavek
--
For that purpose there is a NDEBUG deffinition used all over the sources.