From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: CLI is going to evolve. (was Re: [PATCH] implements MI "-file-list-exec-sections" (updated))
Date: Sat, 08 May 2004 00:57:00 -0000 [thread overview]
Message-ID: <20040508005657.GA2123@nevyn.them.org> (raw)
In-Reply-To: <16540.10964.150176.995095@nick.uklinux.net>
On Sat, May 08, 2004 at 01:33:24AM +0100, Nick Roberts wrote:
>
> The last paragraph you cited was Bob Rossi's, not mine.
>
> Anyway, what's this about?:
>
> > - N:M breakpoints
"break foo" doesn't have to create exactly one breakpoint; but even if
it does, that one breakpoint doesn't have to have a single associated
address. There might be multiple, for instance one at each inlined
copy.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-05-08 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16530.51947.983270.138336@nick.uklinux.net>
[not found] ` <20040501040929.GB17480@white>
[not found] ` <16531.37648.806738.186535@nick.uklinux.net>
[not found] ` <20040502132531.GB1487@white>
[not found] ` <409A9BD3.6050803@gnu.org>
2004-05-08 0:34 ` Nick Roberts
2004-05-08 0:57 ` Daniel Jacobowitz [this message]
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=20040508005657.GA2123@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nick@nick.uklinux.net \
/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