Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: Multiple breakpoint locations
Date: Tue, 13 Nov 2007 20:18:00 -0000	[thread overview]
Message-ID: <20071113201756.GE12593@cox.net> (raw)
In-Reply-To: <18234.1121.556841.49775@kahikatea.snap.net.nz>

On Wed, Nov 14, 2007 at 09:09:05AM +1300, Nick Roberts wrote:
>  > >   (gdb) d 1.1
>  > >   warning: bad breakpoint number at or near '1.1'
>  > 
>  > Well, you can't really delete a location -- if breakpoint expression
>  > corresponds to 20 addresses, that's the way it is -- you cannot delete
>  > some of those addresses from the program ;-)
> 
> It's not immediately obvious, at least to me, so I think this should be
> documented.  Also I think error should be used for the message instead of
> warning as the requested task is not performed. The message could be more
> helpful too:
> 
> (gdb) d 1.1
> This breakpoint cannot be deleted on its own.

Yeah, this is yet another leaky abstraction. The common user has no idea
why multiple breakpoints are created at once, and why they can not
delete only one of the multiple added. 

I like the idea of showing the description. Perhaps with a reason why.

>  > > 2) I can enable/disable 1 and this appears to enable/disable all the
>  > > locations.
>  > >    Perhap this could be documented in the manual.
>  > 
>  > Well yes. Patches welcome ;-)
> 
> I don't want to detract from the fact that you have contributed a major
> patch but I think you should document your own changes.  This is also a
> good idea because you understand the changes best.

Again, this is going to be something that is asked over and over. I
think it'd be great to have it in the manual.

Bob Rossi


  parent reply	other threads:[~2007-11-13 20:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:15 Nick Roberts
2007-11-13 19:28 ` Vladimir Prus
2007-11-13 19:59   ` Daniel Jacobowitz
2007-11-13 20:09   ` Nick Roberts
2007-11-13 20:14     ` Daniel Jacobowitz
2007-11-13 20:18     ` Bob Rossi [this message]
2007-11-13 20:19     ` Vladimir Prus
2007-11-13 22:03     ` Andreas Schwab
2007-11-14  6:20       ` Vladimir Prus
2007-11-14 10:12         ` Andreas Schwab
2007-11-14 21:26           ` Jim Blandy
2007-11-14 21:34             ` Vladimir Prus
2007-11-14 22:08             ` Andreas Schwab
2007-11-15  4:08             ` Eli Zaretskii
2007-11-15 13:37               ` Daniel Jacobowitz
2007-11-15 16:50               ` Jim Blandy
2007-11-13 22:18   ` Eli Zaretskii
2007-11-13 23:39     ` Douglas Evans
2007-11-14  4:17       ` Eli Zaretskii
2007-11-14  5:02         ` Joel Brobecker
2007-11-14  6:13         ` Vladimir Prus
2007-11-14 18:54           ` Eli Zaretskii
2007-11-14 19:00             ` Vladimir Prus
2007-11-17 11:55 ` Eli Zaretskii
2007-11-17 12:07 ` Eli Zaretskii
2007-11-17 14:14   ` Vladimir Prus
2007-11-17 15:36     ` Eli Zaretskii
2007-11-18  1:32       ` Nick Roberts
2007-11-18  2:26         ` Daniel Jacobowitz
2007-11-18  8:47           ` Nick Roberts
2007-11-19 12:57             ` Daniel Jacobowitz

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=20071113201756.GE12593@cox.net \
    --to=bob_rossi@cox.net \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=nickrob@snap.net.nz \
    /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