From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jimb@zwingli.cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Elaborate on new overlay support
Date: Sat, 09 Feb 2002 08:45:00 -0000 [thread overview]
Message-ID: <1858-Sat09Feb2002184407+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <npn0yid3yt.fsf@zwingli.cygnus.com> (message from Jim Blandy on 09 Feb 2002 11:17:46 -0500)
> From: Jim Blandy <jimb@zwingli.cygnus.com>
> Date: 09 Feb 2002 11:17:46 -0500
>
> Are you sure this is the right thing? How breakpoints are implemented
> is usually completely hidden from the user.
Not completely: we have the "hbreak" command, for example.
If you meant to tell that even "break" sometimes sets a hardware
breakpoint, then I agree that it's an internal GDB matter, but if
those are the cases you refer to here, there's no need to explain at
length what hardware breakpoints are, just make a cross-reference to
the "Breakpoints" node, where the detailed explanation should live.
next prev parent reply other threads:[~2002-02-09 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 11:26 Jim Blandy
2002-02-08 23:46 ` Eli Zaretskii
2002-02-09 8:16 ` Jim Blandy
2002-02-09 8:45 ` Eli Zaretskii [this message]
2002-02-09 9:34 ` Andrew Cagney
2002-02-09 10:05 ` Andrew Cagney
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=1858-Sat09Feb2002184407+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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