From: Thomas Neumann <tneumann@users.sourceforge.net>
To: Thomas Neumann <tneumann@users.sourceforge.net>, gdb@sourceware.org
Subject: Re: Organization of breakpoint locations
Date: Mon, 19 Feb 2007 14:40:00 -0000 [thread overview]
Message-ID: <45D99E03.1050309@users.sourceforge.net> (raw)
In-Reply-To: <20070219115744.GC6815@caradoc.them.org>
Daniel Jacobowitz schrieb:
> Have you tested this in any real world use yet? This is only the
> first limitation you'll encounter, I think. For instance, every time
>
hm, I only did manual tests yet. And for a single continue, even a scan
over 50000 breakpoints is not that bad. But I see your point:
Ultimately, this large number of breakpoints comes from automatic
program tracing, which will stop and continue thousands of times.
> these? Your key would not be the address, but the address plus the
> breakpoint sequence number. That handles one and two. Then you can
>
good idea. I thought that a breakpoint could have more than one
bp_location associated with it, preventing such a scheme (but even then
a breakpoint would probably not have more than one location with the
same address).
> To be honest, I don't think this will be a small change either way.
>
I will give the libiberty splay a try, that should be easy. But if
resetting breakpoints is indeed as slow as you indicated, by patch is
probably pointless. What a shame. That would have been a very portable
and nice way to automatically trace execution flow.
Thomas
next prev parent reply other threads:[~2007-02-19 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 11:57 Thomas Neumann
2007-02-19 12:54 ` Daniel Jacobowitz
2007-02-19 14:40 ` Thomas Neumann [this message]
2007-02-19 14:48 ` Daniel Jacobowitz
2007-02-19 14:54 ` Michael Veksler
2007-02-19 21:24 ` Daniel Jacobowitz
2007-02-20 4:46 ` Thomas Neumann
2007-02-20 10:26 ` Thomas Neumann
2007-02-21 17:05 ` Michael Snyder
2007-02-21 1:53 ` Michael Snyder
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=45D99E03.1050309@users.sourceforge.net \
--to=tneumann@users.sourceforge.net \
--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