From: Keith Seitz <keiths@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: Insight Mailing List <insight@sources.redhat.com>
Subject: Re: [RFA] breakpoint balloon info
Date: Thu, 07 Mar 2002 10:43:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0203071042440.5360-100000@makita.cygnus.com> (raw)
In-Reply-To: <200203070828.g278SGx01719@localhost.localdomain>
On Thu, 7 Mar 2002, Martin M. Hunt wrote:
> 2002-03-06 Martin M. Hunt <hunt@redhat.com>
>
> * library/srctextwin.itb (SrcTextWin::showBPBalloon):
> Reformat output. Add conditions, ignore count, commands.
Don't we need to be a little careful about commands? They could be huge...
Anyway, it all looks innocent enough. Does any of this break the srcwin
tests, by chance? I know we test something about BP balloons in there.
Please commit. Thanks,
Keith
> Index: srctextwin.itb
> ===================================================================
> RCS file: /cvs/src/src/gdb/gdbtk/library/srctextwin.itb,v
> retrieving revision 1.32
> diff -u -p -r1.32 srctextwin.itb
> --- srctextwin.itb 2002/03/05 22:22:20 1.32
> +++ srctextwin.itb 2002/03/07 08:25:09
> @@ -2310,27 +2310,36 @@ body SrcTextWin::showBPBalloon {win x y}
> }
>
> set str ""
> - set need_lf 0
> foreach b $bps {
> set bpinfo [gdb_get_breakpoint_info $b]
> lassign $bpinfo file func linenum addr type enabled disposition \
> ignore_count commands cond thread hit_count user_specification
> - if {$thread == "-1"} {set thread "all"}
> set file [lindex [file split $file] end]
> if {$enabled} {
> set enabled "ENA"
> } else {
> set enabled "DIS"
> }
> - if {$cond == ""} {set cond "none"}
> - if {$need_lf} {
> - append str \n
> - } else {
> - set need_lf 1
> +
> + append str [format "breakpoint %d at %s:%d (%#x)\n %s %s %s" \
> + $b $file $linenum $addr $enabled $type $disposition]
> +
> + if {$thread != "-1"} {
> + append str "\n threads: $thread"
> + }
> +
> + if {$ignore_count != 0} {
> + append str "\n ignore: $ignore_count"
> + }
> +
> + if {$cond != ""} {
> + append str "\n condition: $cond"
> + }
> +
> + if {$commands != ""} {
> + append str "\n commands: $commands"
> }
> - append str [format "breakpoint %d at %s:%d (%#x)\n\t%s %s %s %s %s" \
> - $b $file $linenum $addr $enabled $type $disposition \
> - threads=$thread cond=$cond]
> +
> }
>
> # Scope out which break type is set here, and use the tag to get
>
next prev parent reply other threads:[~2002-03-07 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 0:28 Martin M. Hunt
2002-03-07 10:43 ` Keith Seitz [this message]
2002-03-07 12:25 ` Martin M. Hunt
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.GSO.4.33.0203071042440.5360-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=hunt@redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).