From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Sun, 15 Jan 2006 17:50:00 -0000 [thread overview]
Message-ID: <20060115175025.GA7415@nevyn.them.org> (raw)
In-Reply-To: <200601151736.k0FHapQB157574@quasar.engr.sgi.com>
On Sun, Jan 15, 2006 at 09:36:51AM -0800, David Anderson wrote:
> The multiple breakpoints due-to-inlining discussion has
> mentioned 20 or 21 breakpoints.
>
> What if there are 200 or 2000 or 20000 or more inlining sites
> of one function?
>
> A breakpoint listing won't be very usable either, whether of
> 2000 entries or one entry with 2000 break addresses. Will it?
That's why I was not planning on showing the list of locations by
default - you'd have to "drill down" into it for details. Yes, I've
thought about this issue.
It will require changes in lots of other bits of GDB, though. For
instance removing and reinserting all breakpoints becomes impractical.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-15 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 17:38 David Anderson
2006-01-15 17:50 ` Daniel Jacobowitz [this message]
2006-01-15 17:54 ` Robert Dewar
2006-01-15 18:33 ` Andreas Schwab
2006-01-15 19:06 ` Robert Dewar
-- strict thread matches above, loose matches on Subject: below --
2006-01-15 1:51 : " Cyrille Comar
2006-01-15 22:23 ` Paul Hilfinger
2006-01-13 10:42 Paul Hilfinger
2006-01-13 11:32 ` Eli Zaretskii
2006-01-13 11:56 ` Joel Brobecker
2006-01-13 13:05 ` Eli Zaretskii
2006-01-13 14:17 ` Andrew STUBBS
2006-01-13 15:27 ` Daniel Jacobowitz
2006-01-13 15:25 ` Daniel Jacobowitz
2006-01-13 15:19 ` Paul Koning
2006-01-13 15:23 ` Daniel Jacobowitz
2006-01-13 15:40 ` Joel Brobecker
2006-01-14 10:15 ` Paul Hilfinger
2006-01-14 16:16 ` 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=20060115175025.GA7415@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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