Bug #818

[Junior Job] Crashlogs don't contain debug symbols

Added by dalbers over 2 years ago. Updated almost 2 years ago.

Status:Resolved Start date:09/28/2009
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:0.6.0
Version:0.3.0.x OS:Any

Description

Apparently there's an incompatibility concerning the build system and Quassel's internal crash handler (execinfo.h <http://www.gnu.org/software/libc/manual/html_node/Backtraces.html#Backtraces>).

Under certain circumstances the crash logs Quassel produces contain unresolved or null frame pointers, e. g.:

Fatal: ASSERT failure in QList<T>::at: "index out of range", file /usr/include/qt4/QtCore/qlist.h, line 395
#  0 quasselclient        0x0000000000580698 0x0000000000000000
#  1 quasselclient        0x000000000056dc36 0x0000000000000000
#  2 libc.so.6            0x00007fa031a42530 0x0000000000000000
#  3 libc.so.6            0x00007fa031a424b5 gsignal

The crash handler can be triggered by invoking

pkill -SEGV quasselclient
for instance.

History

#1 Updated by dalbers over 2 years ago

This may or may not have to do with the different BUILD_TYPEs Release, RelWithDebugInfo, Debug, Debugfull.

#2 Updated by johu almost 2 years ago

  • Version changed from 0.5-pre to 0.3.0.x

this is done right?

#3 Updated by johu almost 2 years ago

  • Status changed from New to Resolved
  • Target version set to 0.6.0

Also available in: Atom PDF