Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 12:02:00 -0000	[thread overview]
Message-ID: <17958.2099.694416.221119@farnswood.snap.net.nz> (raw)
In-Reply-To: <20070418105813.GA6857@caradoc.them.org>

 > >  > I maybe I could try a patch that introduces a new command that clears
 > >  > all the breakpoints when you load a new file ?
 > > 
 > > I was thinking modifying the GDB environment with the set command, e.g.,
 > > 
 > > set breakpoint auto-clear on/off
 > > 
 > > I think a new command would make behaviour hard to toggle, with a front end
 > > say.
 > > 
 > > I can't approve your patches, so don't do anything yet.  Wait for Daniel
 > > Jacobowitz, for example, to give his opinion.
 > 
 > 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?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-04-18 12:02 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 [this message]
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

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.2099.694416.221119@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