From: "Eli Zaretskii" <eliz@elta.co.il>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8]
Date: Thu, 16 Oct 2003 15:54:00 -0000 [thread overview]
Message-ID: <7137-Thu16Oct2003174852+0200-eliz@elta.co.il> (raw)
In-Reply-To: <16270.44057.973638.26816@localhost.redhat.com> (message from Elena Zannoni on Thu, 16 Oct 2003 10:32:57 -0400)
> From: Elena Zannoni <ezannoni@redhat.com>
> Date: Thu, 16 Oct 2003 10:32:57 -0400
>
> Just occurred to me that maybe the user sometimes would want to set a
> breakpoint in just one particular instance of an inlined function, we
> should still allow that.
How about the following?
(gdb) break inline_foo
Breakpoint 5 set at inline_foo, which has multiple locations.
Say "info breakpoint 5" for more details.
(gdb) info break 5
Num Type Enb Address What
5 sw breakpoint y 0x8040222 inlined into foo
5 sw breakpoint y 0x8040822 inlined into bar
5 sw breakpoint y 0x8040852 inlined into boring_loop
(gdb) delete 5 *0x8040852
> I.e. should setting the multiple breakpoints
> be the default?
I think this is the best default, yes.
Alternatively, we could show all possible addresses where the
requested breakpoint coulod be set and ask the user to select which
ones she wants, like this:
(gdb) break inline_foo
Function inline_foo is inlined into multiple locations:
Address Location
0x8040222 inlined into foo
0x8040822 inlined into bar
0x8040852 inlined into boring_loop
Please use "break *address" to set breakpoints at one or more of these
(gdb) break *0x8040822 *0x8040822
next prev parent reply other threads:[~2003-10-16 15:54 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 16:55 Daniel Jacobowitz
2003-10-08 17:33 ` Elena Zannoni
2003-10-08 19:04 ` Andrew Cagney
2003-10-08 19:07 ` Daniel Jacobowitz
2003-10-08 19:44 ` David Carlton
2003-10-08 20:36 ` Elena Zannoni
2003-10-08 19:49 ` Andrew Cagney
2003-10-08 18:07 ` Jim Blandy
2003-10-08 18:23 ` Joel Brobecker
2003-10-08 19:05 ` Daniel Jacobowitz
2003-10-08 19:52 ` Andrew Cagney
2003-10-08 20:30 ` Daniel Jacobowitz
2003-10-08 21:09 ` Andrew Cagney
2003-10-08 21:11 ` Daniel Jacobowitz
2003-10-08 21:40 ` Elena Zannoni
2003-10-08 22:28 ` Andrew Cagney
2003-10-09 19:19 ` Michael Snyder
2003-10-14 1:38 ` Daniel Jacobowitz
2003-10-14 15:40 ` Andrew Cagney
2003-10-14 15:46 ` David Carlton
2003-10-14 15:51 ` Daniel Jacobowitz
2003-10-14 16:27 ` Elena Zannoni
2003-10-14 20:45 ` Michael Snyder
2003-10-15 15:02 ` Andrew Cagney
2003-10-15 18:20 ` Michael Snyder
2003-10-15 18:30 ` Andrew Cagney
2003-10-15 22:19 ` Michael Snyder
2003-10-15 22:23 ` Andrew Cagney
2003-10-15 22:37 ` Michael Snyder
2003-10-15 18:56 ` Elena Zannoni
2003-10-16 6:59 ` Eli Zaretskii
2003-10-16 13:11 ` Daniel Jacobowitz
2003-10-16 14:08 ` Paul Koning
2003-10-16 14:21 ` Elena Zannoni
2003-10-16 15:54 ` Eli Zaretskii [this message]
2003-10-16 23:20 ` Michael Snyder
2003-10-16 23:18 ` Michael Snyder
2003-10-16 15:45 ` Eli Zaretskii
2003-10-16 23:14 ` Michael Snyder
2003-10-15 22:41 ` Daniel Jacobowitz
2003-10-16 6:55 ` Eli Zaretskii
2003-10-16 14:25 ` Andrew Cagney
2003-10-16 16:02 ` Eli Zaretskii
2003-10-16 23:24 ` Michael Snyder
2003-10-17 6:46 ` Eli Zaretskii
2003-10-17 21:38 ` Michael Snyder
2003-10-18 8:43 ` Eli Zaretskii
2003-10-20 18:48 ` Michael Snyder
2003-10-16 16:16 ` Daniel Jacobowitz
2003-10-16 18:20 ` Andrew Cagney
2003-10-16 23:26 ` Totally OT Michael Snyder
2003-10-16 16:03 ` RFA: Breakpoint infrastructure cleanups [0/8] David Carlton
2003-10-16 16:17 ` Daniel Jacobowitz
2003-10-08 20:55 ` Elena Zannoni
2003-10-08 20:59 ` Daniel Jacobowitz
2003-10-09 6:09 ` Eli Zaretskii
2003-10-09 14:08 ` Daniel Jacobowitz
2003-10-09 17:02 ` Eli Zaretskii
2003-10-09 19:41 ` Daniel Jacobowitz
2003-10-19 16:43 ` Andrew Cagney
2003-10-09 19:33 ` Michael Snyder
2003-10-08 19:38 ` David Carlton
2003-10-08 21:00 ` Daniel Jacobowitz
2003-10-09 6:07 ` Eli Zaretskii
2003-10-08 18:26 ` Eli Zaretskii
2003-10-08 19:09 ` Daniel Jacobowitz
2003-10-19 15:55 ` Andrew Cagney
2003-10-19 16:39 ` Eli Zaretskii
2003-10-30 5:49 ` Daniel Jacobowitz
2003-11-03 18:00 ` Daniel Jacobowitz
2003-11-04 19:57 ` Michael Snyder
[not found] <1065728983.12011.ezmlm@sources.redhat.com>
2003-10-09 20:01 ` Jim Ingham
2003-10-15 19:48 Michael Elizabeth Chastain
2003-10-15 22:00 ` Michael Snyder
2003-10-15 22:14 Michael Elizabeth Chastain
2003-10-15 22:36 ` Michael Snyder
[not found] <1066321046.18949.ezmlm@sources.redhat.com>
2003-10-16 18:58 ` Jim Ingham
2003-10-16 23:30 ` Michael Snyder
2003-10-16 19:02 ` Jim Ingham
2003-10-17 7:04 ` Eli Zaretskii
2003-10-17 16:55 ` Jim Ingham
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=7137-Thu16Oct2003174852+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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