Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [8/9] multiple locations
Date: Wed, 14 Nov 2007 19:21:00 -0000	[thread overview]
Message-ID: <m3wsskab1i.fsf@codesourcery.com> (raw)
In-Reply-To: <fhcuk9$bnh$1@ger.gmane.org> (Vladimir Prus's message of "Tue, 13 Nov 2007 22:40:57 +0300")


Vladimir Prus <ghost at cs.msu.su> writes:
> Daniel Jacobowitz wrote:
>
>> On Tue, Nov 13, 2007 at 11:05:10AM +0300, Vladimir Prus wrote:
>>> > 
>>> > Does the (p) add anything useful to the user?  The manual says:
>>> > 
>>> >       An optional `(p)' suffix marks pending breakpoints
>>> > 
>>> > Is that not clear from the word PENDING?
>>> 
>>> No, because if you set breakpoint in a shared library, and that library
>>> is unloaded, you have some number in 'address' field, but the breakpoint
>>> won't actually fire, and the "(p)" indicates that fact.
>> 
>> Can we just change it back to <PENDING> by discarding the address?
>
> This can actually work. I'll try to implement this idea.

Yeah, that's what I was going to suggest, too --- the number is
basically a dangling pointer once the library's been unloaded.

I agree with Vladimir that the priority of the CLI should be providing
a good command-line experience --- not stability for code trying to
parse the output.  MI has been in GDB in some form or another since
2001.


  reply	other threads:[~2007-11-14 19:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13  7:15 Nick Roberts
2007-11-13  8:05 ` Vladimir Prus
2007-11-13  8:31   ` Nick Roberts
2007-11-13  8:45     ` Vladimir Prus
2007-11-13 12:38   ` Daniel Jacobowitz
2007-11-13 19:58     ` Vladimir Prus
2007-11-14 19:21       ` Jim Blandy [this message]
2007-11-13 22:20   ` Eli Zaretskii
2007-11-13 22:47     ` Joel Brobecker
2007-11-14  6:29       ` Vladimir Prus
2007-11-14  7:06         ` Nick Roberts
2007-11-14 11:58           ` Vladimir Prus
2007-11-14 19:18             ` Nick Roberts
2007-11-14 19:37               ` Joel Brobecker
2007-11-14 19:38               ` Vladimir Prus
2007-11-14 20:42                 ` Nick Roberts
2007-11-14 21:17                   ` Joel Brobecker
2007-11-15 20:39                   ` Vladimir Prus
2007-11-16 20:37                 ` Nick Roberts
2007-11-19  2:42                 ` Nick Roberts
2007-11-14 18:56         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2007-09-07 22:49 Vladimir Prus
2007-09-07 22:51 ` Vladimir Prus
2007-09-08 11:46 ` Eli Zaretskii
2007-09-08 11:55   ` Vladimir Prus
2007-09-08 12:28     ` Eli Zaretskii
2007-09-22 19:53   ` Vladimir Prus
2007-09-23  4:13     ` Eli Zaretskii
2007-09-08 13:17 ` Mark Kettenis

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=m3wsskab1i.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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