From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <alves.ped@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: PR13473 - step N/next N does not trigger gdb.events.stop
Date: Wed, 04 Jan 2012 16:17:00 -0000 [thread overview]
Message-ID: <m3obujbfxg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F047180.5040004@gmail.com> (Pedro Alves's message of "Wed, 04 Jan 2012 15:34:24 +0000")
>>>>> "Pedro" == Pedro Alves <alves.ped@gmail.com> writes:
Pedro> This patch from Khoo Yit Phang (attached to the PR) fixes PR13473.
Thanks.
FWIW, this bug also affects MI.
Pedro> Comments on the test?
Looks good to me.
Tom
next prev parent reply other threads:[~2012-01-04 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 15:34 Pedro Alves
2012-01-04 16:17 ` Tom Tromey [this message]
2012-01-05 13:13 ` Pedro Alves
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=m3obujbfxg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=alves.ped@gmail.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