unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: New function for gdb-ui.el?
Date: Tue, 25 Oct 2005 10:14:19 +0200	[thread overview]
Message-ID: <upspuau90.fsf@gnu.org> (raw)
In-Reply-To: <E1EU5Aj-0004IH-1C@fencepost.gnu.org> (rms@gnu.org)

> From: "Richard M. Stallman" <rms@gnu.org>
> Date: Mon, 24 Oct 2005 12:27:41 -0400
> Cc: emacs-devel@gnu.org
> 
>     > It could go on mouse-2 which has some kind of goto idiom.  Do you think it
>     > should it be restricted to the buffer with the overlay arrow or work on any
>     > file which is part of the source code of the GDB session.
> 
>     I'd restrict it to the former.
> 
> 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.

If by ``this command'' you mean the gdb-ui.el command (as opposed to
the GDB command invoked by gdb-ui.el), then I disagree, for the
reasons explained below.

> But there is an exception: when a function in one file is inlined in
> another.

That's not the only exception; there's also the case of another file
being #include'd in the current frame's source file.  And then there's
the case of a macro defined on another file.  And what about code that
jmp's to another function without building a new stack frame?

In general, I don't think it's gdb-ui's job to enforce such
restrictions on the user, even if these situations are rare.  GDB
already deals with them, so gdb-ui shouldn't bother, since it will
never know enough to DTRT.

Also note that latest versions of GDB have the `advance' command,
which works like `until', but does stop in frames that are inner to
the one where the `advance' command was invoked.  Thus, if the other
source file's function is called by the code in the current frame,
`advance' _will_ stop there.

  parent reply	other threads:[~2005-10-25  8:14 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
2005-10-25  8:14           ` Eli Zaretskii [this message]
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=upspuau90.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.
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).