This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Problems with hook-stop
- From: Daniel Jacobowitz <drow at false dot org>
- To: Carl Shapiro <carl dot shapiro at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 2 Oct 2007 07:41:52 -0400
- Subject: Re: Problems with hook-stop
- References: <4dcb5abd0709260133h10aede86wb60a22094c8d9884@mail.gmail.com> <200709271127.l8RBRMPG017896@brahms.sibelius.xs4all.nl> <4dcb5abd0709271725v73cdf443q46fb43c985474c21@mail.gmail.com> <20070929210750.GA10190@caradoc.them.org> <4dcb5abd0710020057ke69e442q3dc6ca91a9d94cc4@mail.gmail.com>
On Tue, Oct 02, 2007 at 12:57:33AM -0700, Carl Shapiro wrote:
> On 9/29/07, Daniel Jacobowitz <drow@false.org> wrote:
> > Maybe we should handle hooks and commands lists specially when they
> > end in continue or signal. Basically a tail recursion optimization.
>
> If there is no infrastructure in-place to perform this analysis, it
> would seem easier to add a new verb to the GDB command language that
> signals and exits the currently executing command.
Oh, the analysis is trivial. It's doing something with the result of
the analysis that will be harder :-)
--
Daniel Jacobowitz
CodeSourcery