Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [0/9] Breakpoints at multiple locations
Date: Mon, 10 Sep 2007 04:47:00 -0000	[thread overview]
Message-ID: <46E4CC11.8050502@de.ibm.com> (raw)
In-Reply-To: <200709081831.47826.vladimir@codesourcery.com>

Hi Vladimir,

great patch set. I'll test it for our ppc64/spu target. I guess it will be very suitable :-)

Vladimir Prus schrieb:
> 
> Once the library is unloaded, we get:
> 
>         Num Type           Disp Enb  Address    What
>         1   breakpoint     keep y    <MULTIPLE>
>                 breakpoint already hit 2 times
>         1.1                     y(p) 0xb7f9856d helper.hpp:4
>         1.2                     n(p) 0xb7f98588 helper.hpp:4

Just an idea but for my opinion it would be great to have a hit-counter per location like:

         Num Type           Disp Hit Enb  Address    What
         1   breakpoint     keep   8 y    <MULTIPLE>
         1.1                       5 y(p) 0xb7f9856d helper.hpp:4
         1.2                       3 n(p) 0xb7f98588 helper.hpp:4

The <MULTIPLE> entity could add up the counts of all locations.  This would also get rid of the 
annoying "breakpoint already hit xy times" line :-)

What do you think?

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com


  parent reply	other threads:[~2007-09-10  4:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 20:11 Vladimir Prus
2007-09-07 22:18 ` Pierre Muller
2007-09-08 11:57 ` Eli Zaretskii
2007-09-08 14:32   ` Vladimir Prus
2007-09-08 16:27     ` Nathan J. Williams
2007-09-08 16:40       ` Vladimir Prus
2007-09-08 16:52         ` Daniel Jacobowitz
2007-09-10  4:47     ` Markus Deuling [this message]
2007-09-10  7:44       ` Vladimir Prus
2007-09-10 14:11         ` Markus Deuling
2007-09-10 15:38           ` Vladimir Prus

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=46E4CC11.8050502@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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