From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Hilfinger <hilfingr@gnat.com>, gdb@sourceware.org
Subject: Re: [RFC] multiple breakpoints from FILE:LINE
Date: Fri, 13 Jan 2006 11:56:00 -0000 [thread overview]
Message-ID: <20060113115647.GG10275@adacore.com> (raw)
In-Reply-To: <ubqygs6rd.fsf@gnu.org>
> > Normally, this refers to a single location in a program, but if this line
> > is in the middle of a C++ template, a multiply #included file, or an
> > Ada generic definition, it may refer to several locations. Currently,
> > GDB chooses one of these silently.
>
> Shouldn't it set breakpoints on ALL of those places instead?
I think so. Either this, or ask the user to choose. I think the current
situation is partly historical: In C, the situations where this happens
are rare...
> I'm not sure I understand: why isn't something.adb:12 enough to
> specify the breakpoint location unambiguously?
This is because you may have several instances of the same line. Imagine
that you have an inlined function defined at foobar.c:12. The function
body is duplicated at each call of the function. If the user asks to
insert a breakpoint at this line, which instance/address should the
debugger use?
--
Joel
next prev parent reply other threads:[~2006-01-13 11:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 10:42 Paul Hilfinger
2006-01-13 11:32 ` Eli Zaretskii
2006-01-13 11:56 ` Joel Brobecker [this message]
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
2006-01-15 1:51 : " Cyrille Comar
2006-01-15 22:23 ` Paul Hilfinger
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
2006-01-15 19:06 ` Robert Dewar
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=20060113115647.GG10275@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=hilfingr@gnat.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