From: Andreas Schwab <schwab@suse.de>
To: Robert Dewar <dewar@adacore.com>
Cc: David Anderson <davea@quasar.engr.sgi.com>, gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Sun, 15 Jan 2006 18:33:00 -0000 [thread overview]
Message-ID: <jeu0c5s5mr.fsf@sykes.suse.de> (raw)
In-Reply-To: <43CA8C51.1040704@adacore.com> (Robert Dewar's message of "Sun, 15 Jan 2006 12:54:25 -0500")
Robert Dewar <dewar@adacore.com> writes:
> For me, the case of inlining is very different from the case of an
> Ada instantiation or from overloading. I find it hard to imagine
> wanting to breakpoint one particular inline instance.
What if you want to debug a particular function which inlines another
function that is also inlined in many other, frequently called functions?
In this case being able to set a breakpoint in a single instance of the
inline function can considerably reduce the complexity of debugging. Of
course, you can always fall back to setting the breakpoint on an address,
but that makes it difficult to reliably track the breakpoint position when
reloading the binary.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-01-15 18:33 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
2006-01-15 17:54 ` Robert Dewar
2006-01-15 18:33 ` Andreas Schwab [this message]
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=jeu0c5s5mr.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=davea@quasar.engr.sgi.com \
--cc=dewar@adacore.com \
--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