This is the mail archive of the
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: <firstname.lastname@example.org> <200709271127.l8RBRMPG017896@brahms.sibelius.xs4all.nl> <email@example.com> <20070929210750.GA10190@caradoc.them.org> <firstname.lastname@example.org>
On Tue, Oct 02, 2007 at 12:57:33AM -0700, Carl Shapiro wrote:
> On 9/29/07, Daniel Jacobowitz <email@example.com> 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 :-)