From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [0/3] RFC: fix PR mi/8444
Date: Wed, 16 Nov 2011 19:58:00 -0000 [thread overview]
Message-ID: <m3y5vfhmbo.fsf@fleche.redhat.com> (raw)
This series fixes PR mi/8444, plus a few other things I noticed along
the way.
The PR itself concerns getting *stopped notifications when
stop-on-solib-events is enabled. Currently, these notifications do not
have a 'reason' field. I found a few other spots where stop
notifications don't have reasons, this series fixes them all.
Tom
next reply other threads:[~2011-11-16 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 19:58 Tom Tromey [this message]
2011-12-04 14:59 ` Pedro Alves
2011-12-05 21:52 ` RFA: patch NEWS for MI changes (Was: [0/3] RFC: fix PR mi/8444) Tom Tromey
2011-12-06 5:47 ` 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=m3y5vfhmbo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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