From: Eli Zaretskii <eliz@is.elta.co.il>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Improve TUI breakpoint display
Date: Sun, 25 Aug 2002 22:28:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020826075408.23834B-100000@is> (raw)
In-Reply-To: <3D69681C.8070307@nerim.fr>
On Mon, 26 Aug 2002, Stephane Carrez wrote:
> The following patch improves this to:
>
> - have a single place to detect if a source line has a breakpoint
> - display more info about breakpoints.
> The following type marker is displayed (only one of them):
>
> b Breakpoint at line, never hit
> B Breakpoint at line, hit > 0
> h Hardware breakpoint, never hit
> H Hardware breakpoint, hit > 0
>
> In addition, a '+' is displayed for breakpoints that are enabled
> and a '-' is displayed for those disabled.
>
> We can now see: 'B+' or 'b-' instead of '*' in the execution window.
Please add a patch to gdb.texinfo, which currently says a breakpoint is
marked with a lone `*'. Otherwise, TUI users will not be able to figure
out what those indications mean.
Thanks.
next prev parent reply other threads:[~2002-08-26 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-25 14:34 Stephane Carrez
2002-08-25 22:28 ` Eli Zaretskii [this message]
2002-08-30 13:24 ` Stephane Carrez
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=Pine.SUN.3.91.1020826075408.23834B-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=stcarrez@nerim.fr \
/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