From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Dodji Seketeli <dodji@seketeli.org>,
GDB Discuss <gdb@sources.redhat.com>
Subject: Re: question about -file-exec-and-symbols gdbmi command
Date: Wed, 18 Apr 2007 21:55:00 -0000 [thread overview]
Message-ID: <17958.37701.519285.425570@farnswood.snap.net.nz> (raw)
In-Reply-To: <20070418121137.GA19685@caradoc.them.org>
> > > It shouldn't happen automatically. For instance, one use of
> > > -file-exec-and-symbols is to tell GDB that the file has been
> > > recompiled.
> >
> > That's independent of the breakpoint issue, isn't it?
>
> Nope. The difference is that the front end has some knowledge of
> "this is a new program" versus "this is the same program being
> reloaded", because it issued the command in response to some user
> stimulus. GDB has no way to know why the command was issued; in one
> case deleting breakpoints is appropriate, in the other it is not.
>
> So if the front end wants breakpoints deleted, I think it's reasonable
> for it to do so explicitly.
In Emacs at least, GDB command can be entered through the GUD buffer, just like
they are on the command line, so I don't see how it would know the user's
purpose any more than GDB does. Anyway, I have no need of this functionality
at the moment. I'll raise it again when, or if, I need it later
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2007-04-18 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 9:12 Dodji Seketeli
2007-04-18 10:01 ` Nick Roberts
2007-04-18 10:11 ` Dodji Seketeli
2007-04-18 10:38 ` Nick Roberts
2007-04-18 10:58 ` Daniel Jacobowitz
2007-04-18 12:02 ` Nick Roberts
2007-04-18 12:11 ` Daniel Jacobowitz
2007-04-18 13:06 ` Dodji Seketeli
2007-04-18 13:13 ` Daniel Jacobowitz
2007-04-18 21:55 ` Nick Roberts [this message]
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=17958.37701.519285.425570@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dodji@seketeli.org \
--cc=drow@false.org \
--cc=gdb@sources.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