Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
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 12:11:00 -0000	[thread overview]
Message-ID: <20070418121137.GA19685@caradoc.them.org> (raw)
In-Reply-To: <17958.2099.694416.221119@farnswood.snap.net.nz>

On Wed, Apr 18, 2007 at 11:59:47PM +1200, Nick Roberts wrote:
>  > I don't see the point.  If you want to delete breakpoints when you
>  > load a new file, why not just do so?  It's easy with -break-list and
>  > -break-delete.
> 
> I'm thinking that if you load a new program into a front end, there's no need
> to restart GDB, and the user might be surprised to see his old breakpoints are
> still there.  I don't have DDD or Insight to hand to see what they do.
> 
>  > 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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-04-18 12:11 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 [this message]
2007-04-18 13:06             ` Dodji Seketeli
2007-04-18 13:13               ` Daniel Jacobowitz
2007-04-18 21:55             ` Nick Roberts

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=20070418121137.GA19685@caradoc.them.org \
    --to=drow@false.org \
    --cc=dodji@seketeli.org \
    --cc=gdb@sources.redhat.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox