From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] problem fetching inferior memory due to breakpoint
Date: Thu, 27 Apr 2006 02:10:00 -0000 [thread overview]
Message-ID: <20060427021030.GA13830@nevyn.them.org> (raw)
In-Reply-To: <4450204A.1020503@redhat.com>
On Wed, Apr 26, 2006 at 06:37:14PM -0700, Michael Snyder wrote:
> If the breakpoints_inserted flag were made globally available
> (thru an accessor method, of course), then there is a really
> inexpensive way to determine that the list-walking step may
> be skipped.
Right, but my point is that the concept of an "all breakpoints are
inserted" flag may have its days numbered. If we want to scale
to large numbers of breakpoints - e.g. on an inlined function -
I don't think we can remove all breakpoints.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-27 2:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 19:05 Joel Brobecker
2006-04-26 19:19 ` Daniel Jacobowitz
2006-04-26 21:18 ` Joel Brobecker
2006-04-26 21:39 ` Daniel Jacobowitz
2006-04-26 22:18 ` Joel Brobecker
2006-04-26 22:29 ` Daniel Jacobowitz
2006-04-26 23:33 ` Michael Snyder
2006-04-27 0:42 ` Daniel Jacobowitz
2006-04-27 1:37 ` Michael Snyder
2006-04-27 2:10 ` Daniel Jacobowitz [this message]
2006-04-27 0:53 ` Jim Blandy
2006-04-27 20:28 ` Eli Zaretskii
2006-04-27 20:56 ` Joel Brobecker
2006-04-28 5:12 ` Eli Zaretskii
2006-04-28 17:00 ` Joel Brobecker
2006-04-28 17:45 ` Daniel Jacobowitz
2006-04-29 14:14 ` Eli Zaretskii
2006-04-29 14:20 ` Daniel Jacobowitz
2006-04-29 14:48 ` Eli Zaretskii
2006-04-29 15:06 ` Daniel Jacobowitz
2006-04-29 15:18 ` Daniel Jacobowitz
2006-04-29 17:10 ` Eli Zaretskii
2006-04-29 14:14 ` 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=20060427021030.GA13830@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@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