This is the mail archive of the archer@sourceware.org mailing list for the Archer project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: uw_install_context() and GDB

From: Tom Tromey <tromey at redhat dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Phil Muldoon <pmuldoon at redhat dot com>, Daniel Jacobowitz <drow at false dot org>, Project Archer <archer at sourceware dot org>, jason at redhat dot com
Date: Thu, 14 Aug 2008 14:39:17 -0600
Subject: Re: uw_install_context() and GDB
References: <48A46168.7070300@redhat.com><20080814173235.GA15077@caradoc.them.org><48A47253.1060705@redhat.com> <m3abffig2t.fsf@google.com>
Reply-to: Tom Tromey <tromey at redhat dot com>

>>>>> "Ian" == Ian Lance Taylor <iant@google.com> writes:

Ian> I agree that "next" over a function call that throws an exception past
Ian> the current stack frame should ideally stop in a user written
Ian> destructor.  It shouldn't stop for destructors in functions below the
Ian> current stack frame.

Yeah, I agree.

Ian> That is (the functions are not presented in the order in which they
Ian> are called):

Thanks for this.  I think cases like this can be pretty clearly
expressed as test cases ... Keith is already taking this tack with
expression handling.

Tom

References:
- uw_install_context() and GDB
  - From: Phil Muldoon
- Re: uw_install_context() and GDB
  - From: Daniel Jacobowitz
- Re: uw_install_context() and GDB
  - From: Phil Muldoon
- Re: uw_install_context() and GDB
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]