This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/16087] cannot step in catch block after exception is thrown
- From: "sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 04 Nov 2013 04:57:01 +0000
- Subject: [Bug breakpoints/16087] cannot step in catch block after exception is thrown
- Auto-submitted: auto-generated
- References: <bug-16087-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16087
--- Comment #3 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to Toma Bilius from comment #2)
> I tested with GDB 7.6.1 and the behavior is the same (compiler version is
> 4.6.3). Unfortunately updating the compiler is a more complex task for our
> project. Does the new version of GCC insert a default probe that GDB will
> look after when installing the breakpoints?
Yeah, just updating GDB won't solve the problem. It needs support from the GCC
side (libgcc specifically), and you won't have it until you update GCC.
Newer versions of GCC provide a probe located at libgcc which makes it possible
for GDB to do what you want. I implemented it with the following patch:
<http://gcc.gnu.org/ml/gcc-patches/2011-11/msg02246.html>
As you can see there, before the patch libgcc for ARM did not provide even
_Unwind_DebugHook, so it is not possible to use it even without probes... I
can't think of anything you could do except updating the GCC version you are
using (maybe someone else can, let's wait to see if others can say something
about this).
If nobody answers in a few days, I will close this as INVALID because it is not
GDB's fault, and because your GCC version does not provide the necessary
infrastructure unfortunately. But please, don't hesitate to reopen this bug if
you have some new information about this.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.