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
Cc: gdb@sources.redhat.com
Subject: Re: stop-on-solib-events and Cygwin (or MinGW)
Date: Thu, 14 Feb 2008 19:20:00 -0000	[thread overview]
Message-ID: <fp245b$i9g$1@ger.gmane.org> (raw)
In-Reply-To: <20080214190527.GA10813@caradoc.them.org>

Daniel Jacobowitz wrote:

> On Thu, Feb 14, 2008 at 10:58:02AM -0800, Gordon Prieur wrote:
>> Its similar to 2369 but there are several differences. First off, I'm
>> running  in mi mode
>> and I don't really expect it to handle breakpoints in unloaded dlls. In
>> command line, it
>> asks if it should be left "pending on future shared library load".
> 
> Vladimir added support for this to GDB/MI on 2007-12-14.
> 
> Vladimir, I noticed there's no NEWS entry for this.  If you agree
> there should be, could you add one?

What about the below?

- Volodya

diff --git a/gdb/NEWS b/gdb/NEWS
index e87ee01..84ab160 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -62,6 +62,9 @@ Decimal Floating Point extension.  In addition, the PowerPC target
 now has a set of pseudo-registers to inspect decimal float values
 stored in two consecutive float registers.

+* The -break-insert MI command can optionally create pending
+breakpoints now.
+
 * New commands

 set print frame-arguments (all|scalars|none)



       reply	other threads:[~2008-02-14 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47B473F8.5050401@sun.com>
     [not found] ` <20080214170852.GA3552@caradoc.them.org>
     [not found]   ` <47B47D3B.8050708@sun.com>
     [not found]     ` <20080214181353.GA7518@caradoc.them.org>
     [not found]       ` <47B48F3A.7070002@sun.com>
     [not found]         ` <20080214190527.GA10813@caradoc.them.org>
2008-02-14 19:20           ` Vladimir Prus [this message]
2008-02-14 19:43             ` Eli Zaretskii

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='fp245b$i9g$1@ger.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@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