From: "Carl Shapiro" <carl.shapiro@gmail.com>
To: gdb@sourceware.org
Subject: Re: Problems with hook-stop
Date: Tue, 02 Oct 2007 07:57:00 -0000 [thread overview]
Message-ID: <4dcb5abd0710020057ke69e442q3dc6ca91a9d94cc4@mail.gmail.com> (raw)
In-Reply-To: <20070929210750.GA10190@caradoc.them.org>
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.
next prev parent reply other threads:[~2007-10-02 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 16:06 Carl Shapiro
2007-09-27 12:06 ` Mark Kettenis
2007-09-28 1:23 ` Carl Shapiro
2007-09-29 21:44 ` Daniel Jacobowitz
2007-10-02 7:57 ` Carl Shapiro [this message]
2007-10-02 11:42 ` Daniel Jacobowitz
2007-09-27 12:35 ` Christian Thalinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dcb5abd0710020057ke69e442q3dc6ca91a9d94cc4@mail.gmail.com \
--to=carl.shapiro@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox