This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/22733] Segfault in frame_unwind_pc when attempting to show backtrace
- From: "b7.10110111 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 19 Jan 2018 11:34:40 +0000
- Subject: [Bug backtrace/22733] Segfault in frame_unwind_pc when attempting to show backtrace
- Auto-submitted: auto-generated
- References: <bug-22733-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22733
--- Comment #1 from Ruslan <b7.10110111 at gmail dot com> ---
Note that if I run qmake without CONFIG+=debug, i.e. in the default mode
without debug info, then the #1 line of GDB-printed backtrace looks like
#1 0x00007ffff7ad86e7 in QPatternist::ReportContext::createError
(this=this@entry=0x654080, description="Premature end of document.",
type=type@entry=QtFatalMsg, id=Python Exception <class 'gdb.error'> cannot
resolve overloaded method `data': no arguments supplied:
, sourceLocation=...)
I.e. instead of crash we get "Python Exception...".
In case this matters, Qt5 I was testing on has version 5.5.1 compiled from the
official source tarball, with debug info enabled.
--
You are receiving this mail because:
You are on the CC list for the bug.