From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sources.redhat.com
Subject: Re: Multiple breakpoint locations
Date: Sat, 17 Nov 2007 12:07:00 -0000 [thread overview]
Message-ID: <u8x4xcbyj.fsf@gnu.org> (raw)
In-Reply-To: <18233.63439.953202.586908@kahikatea.snap.net.nz> (message from Nick Roberts on Wed, 14 Nov 2007 08:15:27 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Wed, 14 Nov 2007 08:15:27 +1300
>
>
> The new code for breakpoints with multiple locations looks very good and
> addresses a common complaint about GDB. I have a couple of points and
> apologise if they have already been discussed.
Btw, while working on Nick's proposals, I found myself confused wrt
the connection, if any, between the feature described in "Breakpoint
Menus" and the multiple-location breakpoints that was the subject of
this thread.
Are these features the same (i.e., is the format of the
multiple-locations breakpoint listing described in "Set Break" what we
use for breakpoints set from the menu described in "Breakpoint
Menus")? Or are they two different features?
If the former, won't additional locations, which we didn't select from
the menu, appear in the list of locations as result of loading shared
libraries that define additional overloaded variants of the function
in which we wanted to break?
If the latter, I cannot seem to find the description of how multiple
locations come into existence in the first place anywhere in the
manual. Am I missing something?
next prev parent reply other threads:[~2007-11-17 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 19:15 Nick Roberts
2007-11-13 19:28 ` Vladimir Prus
2007-11-13 19:59 ` Daniel Jacobowitz
2007-11-13 20:09 ` Nick Roberts
2007-11-13 20:14 ` Daniel Jacobowitz
2007-11-13 20:18 ` Bob Rossi
2007-11-13 20:19 ` Vladimir Prus
2007-11-13 22:03 ` Andreas Schwab
2007-11-14 6:20 ` Vladimir Prus
2007-11-14 10:12 ` Andreas Schwab
2007-11-14 21:26 ` Jim Blandy
2007-11-14 21:34 ` Vladimir Prus
2007-11-14 22:08 ` Andreas Schwab
2007-11-15 4:08 ` Eli Zaretskii
2007-11-15 13:37 ` Daniel Jacobowitz
2007-11-15 16:50 ` Jim Blandy
2007-11-13 22:18 ` Eli Zaretskii
2007-11-13 23:39 ` Douglas Evans
2007-11-14 4:17 ` Eli Zaretskii
2007-11-14 5:02 ` Joel Brobecker
2007-11-14 6:13 ` Vladimir Prus
2007-11-14 18:54 ` Eli Zaretskii
2007-11-14 19:00 ` Vladimir Prus
2007-11-17 11:55 ` Eli Zaretskii
2007-11-17 12:07 ` Eli Zaretskii [this message]
2007-11-17 14:14 ` Vladimir Prus
2007-11-17 15:36 ` Eli Zaretskii
2007-11-18 1:32 ` Nick Roberts
2007-11-18 2:26 ` Daniel Jacobowitz
2007-11-18 8:47 ` Nick Roberts
2007-11-19 12:57 ` 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=u8x4xcbyj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.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