From: Nick Roberts <nickrob@snap.net.nz>
To: Dodji Seketeli <dodji@seketeli.org>
Cc: GDB Discuss <gdb@sources.redhat.com>
Subject: Re: question about -file-exec-and-symbols gdbmi command
Date: Wed, 18 Apr 2007 10:01:00 -0000 [thread overview]
Message-ID: <17957.60377.419260.20236@farnswood.snap.net.nz> (raw)
In-Reply-To: <20070418111206.45c55d72@coin>
> I am using gdb with the mi2 interpreter.
>
> I do -file-exec-and-symbols <prog-1>, set a couple of
> breakpoints, do a bit of debugging a bit etc.
>
> Then I do a -file-exec-and-symbols <prog-2> .
> At this point, gdb tries to set the breakpoint I have set previously,
> while debugging <prog-1>. Of course, that attempt fails. Is this
> behavious normal ? I would have thought that gdb should clear the
> current breakpoints when -file-exec-and-symbols is run on a new exec
> file.
-file-exec-and-symbols is really just the `file' command:
In mi-cmds.c:
{ "file-exec-and-symbols", { "file", 1 }, NULL, NULL },
so it's not restricted to MI.
I don't really use either but maybe it would be inconvenient to have all
the breakpoints cleared, if you wanted to switch to another version of the
same program, say. It's easier to delete then all manually, just with `delete'
than it is to add them back again.
Perhaps it could be a GDB option.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-04-18 10:01 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 [this message]
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
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=17957.60377.419260.20236@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dodji@seketeli.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