From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: MI: changing breakpoint location
Date: Thu, 16 Mar 2006 23:12:00 -0000 [thread overview]
Message-ID: <17433.61359.500131.182453@kahikatea.snap.net.nz> (raw)
In-Reply-To: <dvc0k6$fgm$1@sea.gmane.org>
> Now, I have to delete the old breakpoint and create the new one, which is
> workable, but not convenient.
I don't find a problem with that, but it would be nice if when a program is
edited and recompiled that GDB could track the line number. So, for example
if the breakpoint is on line 10, say, and lines 4 and 5 are deleted, then
after recompiling and restarting, its on line 8. I think Visual Stuio has
this feature. I have no idea how easy/hard it would be to implement.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-03-16 23:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 15:43 Vladimir Prus
2006-03-16 15:48 ` Bob Rossi
2006-03-16 16:05 ` Vladimir Prus
2006-03-16 16:12 ` Daniel Jacobowitz
2006-03-16 16:16 ` Vladimir Prus
2006-03-16 16:40 ` Daniel Jacobowitz
2006-03-16 16:46 ` Vladimir Prus
2006-03-16 17:11 ` Daniel Jacobowitz
2006-03-17 10:46 ` Vladimir Prus
2006-03-17 18:28 ` Daniel Jacobowitz
2006-03-17 17:43 ` Daniel Jacobowitz
2006-03-17 11:03 ` Eli Zaretskii
2006-03-17 10:57 ` Eli Zaretskii
2006-03-16 23:12 ` Nick Roberts [this message]
2006-03-16 23:23 ` Daniel Jacobowitz
2006-03-16 23:25 ` David Daney
2006-03-16 23:54 ` Daniel Jacobowitz
2006-03-17 13:20 ` Eli Zaretskii
2006-03-17 17:34 ` Daniel Jacobowitz
2006-03-18 18:46 ` Eli Zaretskii
2006-03-16 23:56 ` Nick Roberts
2006-03-17 10:55 ` Vladimir Prus
2006-03-17 11:42 ` Eli Zaretskii
2006-03-17 0:04 ` Daniel Jacobowitz
2006-03-17 0:23 ` Joel Brobecker
2006-03-17 3:57 ` Jim Ingham
2006-03-17 11:40 ` Eli Zaretskii
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=17433.61359.500131.182453@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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