From: "Marcin Kościelnicki" <koriakin@0x04.net>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite/gdb.trace: Fix expected message on continue.
Date: Tue, 19 Jan 2016 12:08:00 -0000 [thread overview]
Message-ID: <569E2735.6090906@0x04.net> (raw)
In-Reply-To: <569E240C.7030702@redhat.com>
On 19/01/16 12:54, Pedro Alves wrote:
> On 01/19/2016 11:33 AM, Marcin KoÅcielnicki wrote:
>> This is fallout from f303dbd60d9c7984832446eeb9d4e4d89703c615.
>>
>> gdb/testsuite/ChangeLog:
>>
>> * gdb.trace/ftrace.exp: Fix expected message on continue.
>> * gdb.trace/pending.exp: Fix expected message on continue.
>> * gdb.trace/trace-break.exp: Fix expected message on continue.
>
> Took me a couple minutes to understand why we show thread numbers in these
> tests, given that they're single-threaded. Eventually I figured out that
> it was because they load the IPA library, which injects a thread in
> the inferior, making it multithreaded.
>
>> ---
>> OK to push?
>
> OK, but please add something like the above to the commit log.
>
> Thanks,
> Pedro Alves
>
Thanks, pushed.
prev parent reply other threads:[~2016-01-19 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:33 Marcin Kościelnicki
2016-01-19 11:54 ` Pedro Alves
2016-01-19 12:08 ` Marcin Kościelnicki [this message]
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=569E2735.6090906@0x04.net \
--to=koriakin@0x04.net \
--cc=gdb-patches@sourceware.org \
--cc=palves@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