This is the mail archive of the
mailing list for the Archer project.
Re: uw_install_context() and GDB
- From: Daniel Jacobowitz <drow at false dot org>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: Project Archer <archer at sourceware dot org>, jason at redhat dot com
- Date: Thu, 14 Aug 2008 13:32:35 -0400
- Subject: Re: uw_install_context() and GDB
- References: <48A46168.email@example.com>
On Thu, Aug 14, 2008 at 05:46:32PM +0100, Phil Muldoon wrote:
> The first was modifying the "next" command to place an
> implementation-internal breakpoint in __cxa_begin_catch, and comparing
> frames. (Is the frame that "next" was performed on above the
> current-frame? If so stop). But this method would skip any user-written
> destructors in the _UA_CLEANUP_PHASE. If any user-written destructors
> exist in the frame "next" was run on, or any frame inbetween that and the
> exception-handler, then the inferior should be stopped there - at the
> first one. This would be the proper behaviour for "next". Placing a
> breakpoint in __cxa_begin_catch would skip those. So I do not think this
> method is suitable.
I think you have to justify that assertion ("this would be the proper
behavior"). Why would it be? They're like signal handlers or
function calls; breakpoints in them would stop the program, but I
don't see a reason "next" should see them.