From: Doug Evans <dje@transmeta.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Matt Thomas <matt@3am-software.com>,
Michael Snyder <msnyder@redhat.com>,
gdb@sources.redhat.com
Subject: Re: breakpoint commands and finish
Date: Thu, 17 Apr 2003 21:19:00 -0000 [thread overview]
Message-ID: <16031.6671.349328.837129@casey.transmeta.com> (raw)
In-Reply-To: <20030417204953.GA26080@nevyn.them.org>
Daniel Jacobowitz writes:
> The macro facility isn't, but a command could be added to do this
> without much trouble.
For my own education, what's missing?
> I would rather us discuss the semantics of
> commands lists containing commands which resume the inferior. There
> must be a more user-useful way to approach it than we do now.
What if you allowed multiple "resume" commands in the "top level"
breakpoint only, and allowed "nested" breakpoints only if they
either stopped execution (in which case execution stops) or if
the only "resume" they did was a tail-call-like continue.
If a nested breakpoint's command list does a resumption with a
non-tail-continue, execution stops.
next prev parent reply other threads:[~2003-04-17 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 20:56 Matt Thomas
2003-04-14 21:00 ` Joel Brobecker
2003-04-14 21:04 ` Joel Brobecker
2003-04-14 21:11 ` Doug Evans
2003-04-14 21:33 ` Joel Brobecker
2003-04-14 22:27 ` Doug Evans
2003-04-14 21:23 ` Matt Thomas
2003-04-17 17:47 ` Michael Snyder
2003-04-17 18:48 ` Matt Thomas
2003-04-17 20:19 ` Daniel Jacobowitz
2003-04-17 20:44 ` Doug Evans
2003-04-17 20:50 ` Daniel Jacobowitz
2003-04-17 21:19 ` Doug Evans [this message]
2003-04-17 21:44 ` Daniel Jacobowitz
2003-04-17 23:11 ` return value of a gdb command Smita
2003-04-17 23:13 ` Daniel Jacobowitz
2003-04-18 12:10 ` Bob Rossi
2003-04-18 13:38 ` Daniel Jacobowitz
2003-04-21 20:55 ` Andrew Cagney
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=16031.6671.349328.837129@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=matt@3am-software.com \
--cc=msnyder@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).