From: Eli Zaretskii <eliz@gnu.org>
Cc: nickrob@snap.net.nz, ich@frank-schmitt.net, emacs-devel@gnu.org
Subject: Re: New function for gdb-ui.el?
Date: Wed, 26 Oct 2005 08:43:01 +0200 [thread overview]
Message-ID: <umzkwkccq.fsf@gnu.org> (raw)
In-Reply-To: <E1EUVNy-0008PU-MD@fencepost.gnu.org> (rms@gnu.org)
> From: "Richard M. Stallman" <rms@gnu.org>
> Date: Tue, 25 Oct 2005 16:27:06 -0400
> Cc: ich@frank-schmitt.net, emacs-devel@gnu.org
>
> > To move to another file usually means moving to another frame, and
> > that's not the job of `until'. This command should refuse
> > to move to another frame.
>
> Yes, you're right.
>
> Actually, now I am not sure what I said is true. Maybe `until' just
> sets a temporary breakpoint and continues. If so, it would actually
> "work" even if you specify a line in a different function.
If you give `until' an argument, it does set a temporary breakpoint,
but when it breaks, GDB checks that it is in the same frame as where
the `until' command was given, and if it isn't, it doesn't stop the
program.
next prev parent reply other threads:[~2005-10-26 6:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 9:14 New function for gdb-ui.el? Nick Roberts
2005-10-23 11:56 ` Eli Zaretskii
2005-10-23 20:25 ` Nick Roberts
2005-10-23 21:53 ` Kim F. Storm
2005-10-24 6:33 ` Nick Roberts
2005-10-24 11:46 ` Kim F. Storm
2005-10-24 22:07 ` Kim F. Storm
2005-10-24 22:29 ` Nick Roberts
2005-10-25 1:27 ` Nick Roberts
2005-10-25 9:12 ` Kim F. Storm
2005-10-23 20:43 ` Frank Schmitt
2005-10-24 6:57 ` Nick Roberts
2005-10-24 7:35 ` Frank Schmitt
2005-10-24 16:27 ` Richard M. Stallman
2005-10-24 20:26 ` Nick Roberts
2005-10-25 20:27 ` Richard M. Stallman
2005-10-25 23:00 ` Nick Roberts
2005-10-26 6:49 ` Eli Zaretskii
2005-10-26 8:58 ` Nick Roberts
2005-10-26 15:02 ` gcc and inline [was: Re: New function for gdb-ui.el?] Tomas Zerolo
2005-10-26 19:32 ` Eli Zaretskii
2005-10-26 20:20 ` Andreas Schwab
2005-10-27 4:22 ` Tomas Zerolo
2005-10-27 5:01 ` Eli Zaretskii
2005-10-28 3:47 ` Richard M. Stallman
2005-10-28 8:29 ` Eli Zaretskii
2005-10-28 8:34 ` Tomas Zerolo
2005-10-28 11:19 ` Miles Bader
2005-10-26 19:31 ` New function for gdb-ui.el? Eli Zaretskii
2005-10-27 1:30 ` Richard M. Stallman
2005-10-28 10:54 ` David Hansen
2005-10-28 12:22 ` Miles Bader
2005-10-28 21:14 ` Nick Roberts
2005-10-29 13:02 ` David Hansen
2005-10-29 20:37 ` Nick Roberts
2005-10-30 0:11 ` Miles Bader
2005-10-30 22:33 ` Nick Roberts
2005-10-26 6:43 ` Eli Zaretskii [this message]
2005-10-25 8:14 ` Eli Zaretskii
2005-10-23 21:26 ` Kim F. Storm
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=umzkwkccq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ich@frank-schmitt.net \
--cc=nickrob@snap.net.nz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).