Message: previous - next
Month: May 2012

Re: [trinity-devel] Konqueror SIGABRT with latest GIT

From: Darrell Anderson <humanreadable@...>
Date: Wed, 16 May 2012 19:02:27 -0700 (PDT)
> It could be d3a9d561, though I don't know how.  I
> assume you rebuilt tdelibs, then rebuilt all the other packages against
> it?  d3a9d561 introduced an ABI incompatibility.

Yes I did, but...

This afternoon I again rebuilt both tdelibs and tdebase. This time without stripping the debug symbols. The packages sizes were much larger of course. All seemed to be going well.

I still get the same crash from Konqueror, but the crash dialog informs me "This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash."

I receive the same crash message when I run the crashtest binary, which is intended exactly for this purpose.

For the moment I'm assuming I'm doing something wrong. What is the correct way to build with debugging symbols?