Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Debugging a Vlc dll with GDB.
Date: Fri, 07 Dec 2007 14:09:00 -0000	[thread overview]
Message-ID: <fjbjmt$naf$1@ger.gmane.org> (raw)
In-Reply-To: <4758A871.9060508@portugalmail.pt>

Pedro Alves wrote:

> Daniel Jacobowitz wrote:
>> On Fri, Dec 07, 2007 at 12:28:42AM +0000, Pedro Alves wrote:
>>> I could swear there use to be a "pending resolved"
>>> notice.  Did it go away with the multiple breakpoint
>>> location support?
>> 
>> Yes, I believe so.  It was mostly there to warn you that the
>> breakpoint number had changed, which Vladimir has now fixed.
>> 
> 
> Humm, I found it useful, as in "ok, the breakpoint I set in a
> function that will only trigger after I do this, that, and that,
> is correctly set".  Now, I have to interrupt the inferior and
> do an info breakpoints to see if it got in.

Well, in MI any change of breakpoint should result in a notification --
though it does not do now. 

I have no idea whatsoever what should CLI do, but it seems to be strange
that you have to regularly check if your breakpoint is set -- is GDB
*that* buggy?

- Volodya



  parent reply	other threads:[~2007-12-07 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071206182343.GA16137@caradoc.them.org>
     [not found] ` <433908.24398.qm@web57701.mail.re3.yahoo.com>
     [not found]   ` <20071206202850.GA27429@caradoc.them.org>
     [not found]     ` <47586224.CE80C330@dessent.net>
2007-12-07  0:42       ` Pedro Alves
2007-12-07  0:53         ` Daniel Jacobowitz
2007-12-07  6:20           ` Pedro Alves
2007-12-07 14:00             ` Daniel Jacobowitz
2007-12-08 11:42               ` Eli Zaretskii
2007-12-07 14:09             ` Vladimir Prus [this message]
2007-12-07 21:24           ` Dave Korn

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='fjbjmt$naf$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@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