From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Skip async-shell.exp if displaced stepping is not supported
Date: Fri, 15 Jul 2011 02:11:00 -0000 [thread overview]
Message-ID: <20110714222542.GA32454@host1.jankratochvil.net> (raw)
In-Reply-To: <m3hb6od9tc.fsf@fleche.redhat.com>
On Thu, 14 Jul 2011 19:57:35 +0200, Tom Tromey wrote:
> >>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
> Yao> 2011-07-14 Yao Qi <yao@codesourcery.com>
> Yao> * gdb.python/py-evthreads.exp: Likewise.
[...]
> I had thought that the py-evthreads.exp test was changed not to rely on
> non-stop, but I must have been mistaken.
It still relies on non-stop. More discussed is at filed PR:
event.inferior_thread does not exist in all-stop/sync mode
http://sourceware.org/bugzilla/show_bug.cgi?id=12967
Thanks,
Jan
next prev parent reply other threads:[~2011-07-14 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 7:09 Yao Qi
2011-07-13 14:28 ` Tom Tromey
2011-07-14 17:25 ` Yao Qi
2011-07-14 22:26 ` Tom Tromey
2011-07-15 2:11 ` Jan Kratochvil [this message]
2011-07-18 15:01 ` [committed] " Yao Qi
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=20110714222542.GA32454@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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