From: Tom Tromey <tromey@redhat.com>
To: Insight List <insight@sourceware.cygnus.com>
Subject: Thoughts on saving breakpoints
Date: Fri, 22 Dec 2000 23:54:00 -0000 [thread overview]
Message-ID: <87y9x71rsx.fsf@creche.redhat.com> (raw)
Last week I did some debugging and I had an experience which helped me
understand why I think breakpoints should be saved the way I think
they should be saved.
I was debugging gcc, and (thought I :-) found my bug. I fixed it and
rebuilt gcc without stopping insight. When I re-ran the inferior, gdb
re-read the gcc executable, recomputed (I presume) and reinserted my
breakpoints, and then actually restarted the debuggee.
My feeling is that saving the Insight session and restarting it should
have roughly the same user-visible effect as recompiling the
inferior's executable.
We all know there's no perfect way to save and restore breakpoints due
to possible changes in the inferior. However, I think that if we
adopt the same strategy that gdb itself uses when re-reading the
executable, then this will be the least suprising to the user. I for
one would find it confusing if gdb and Insight adopted different
heuristics here.
Tom
reply other threads:[~2000-12-22 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y9x71rsx.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).