From: Joel Brobecker <brobecker@adacore.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Faster stepping amidst breakpoints
Date: Tue, 01 Feb 2011 03:23:00 -0000 [thread overview]
Message-ID: <20110201032338.GI2384@adacore.com> (raw)
In-Reply-To: <20110131151229.GA2915@caradoc.them.org>
> As far as I can remember (you know how much GDB development I do
> nowadays), the only risks were if GDB crashed and left the application
> with breakpoints inserted. Of course, I'm in favor of GDB not
> crashing.
I see this as an acceptable outcome of a debugger crash. I am guessing
that in most cases, people debug their program, and then want it killed,
so leaving the inferior behind with breakpoints inserted won't matter
much (or, not as much as having their session brutally interrupted by
the crash itself). For the small number of those for whom it matters,
they can change the switch back...
I was more worried about possible issues during normal operations.
For instance, has this been tested with software-single-step, for
instance? What I'm going to do, to give it a little more exposure,
is flip the switch in AdaCore's HEAD build, and monitor the testsuite
results. Have you flipped the switch in CS's builds too?
--
Joel
next prev parent reply other threads:[~2011-02-01 3:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 15:06 Maxim Grigoriev
2011-01-24 8:04 ` Daniel Jacobowitz
2011-01-24 21:08 ` Maxim Grigoriev
2011-01-31 7:47 ` Joel Brobecker
2011-01-31 15:39 ` Daniel Jacobowitz
2011-02-01 3:23 ` Joel Brobecker [this message]
2011-02-01 18:44 ` Michael Snyder
2011-02-03 4:55 ` Joel Brobecker
2011-02-02 17:10 ` Daniel Jacobowitz
2011-02-03 4:46 ` Joel Brobecker
2011-02-13 15:17 ` Mark Kettenis
2011-02-14 3:27 ` Joel Brobecker
2011-02-14 10:50 ` Joel Brobecker
2011-02-01 15:12 ` Pedro Alves
2011-02-03 22:54 ` Maxim Grigoriev
2011-02-04 16:06 ` Tom Tromey
2011-02-04 19:32 ` Maxim Grigoriev
2011-02-04 16:33 ` Daniel Jacobowitz
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=20110201032338.GI2384@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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