This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Force to update thread list in queue-signal.exp
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 10 Oct 2014 10:18:40 +0100
- Subject: Re: [PATCH] Force to update thread list in queue-signal.exp
- Authentication-results: sourceware.org; auth=none
- References: <1411644946-11697-1-git-send-email-yao at codesourcery dot com> <87bnpougtx dot fsf at codesourcery dot com> <5434032E dot 9070504 at redhat dot com> <877g0at7mi dot fsf at codesourcery dot com>
On 10/09/2014 01:21 AM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>>>> * gdb.threads/queue-signal.exp: Execute command "info threads".
>>
>> This part should no longer be necessary:
>>
>> https://sourceware.org/ml/gdb-patches/2014-09/msg00734.html
>
> Thanks for the pointer. I didn't follow this patch series because
> ThunderBird hides it under other unrelated thread.
Odd. I sent it as a separate thread with git send-email.
The cover letter has no In-Reply-To or References headers even.
My Thunderbird doesn't put it under any other thread, and the
archives have it as a separate thread too.
But now that you mention this, I had found odd that this series
https://sourceware.org/ml/gdb-patches/2014-09/msg00772.html
had been sent as reply to an unrelated old email from 2012, but,
now that I look at the raw headers of Jose's email, it doesn't seem
to have been send as response to any email after all, but rather
it's my Thunderbird that's acting up. gmane doesn't nest that under
what my TB is nesting it under either, this:
http://thread.gmane.org/gmane.comp.gdb.patches/75048
Jose's mail's headers have:
Message-Id: <1411724905-31234-1-git-send-email-jose.marchesi@oracle.com>
In-Reply-To: <no>
References: <no>
And the message my TB nests it under has:
Message-Id: <1334741131-29283-1-git-send-email-Hilfinger@adacore.com>
In-Reply-To: <no>
References: <no>
I wondered if those "<no>"s triggered that, but my email doesn't
have it, so that wouldn't explain it for your case.
Sounds like we're both hitting the same Thunderbird bug still.
I'm running version 31.1.1 on Fedora 20.
> Looks other tests don't have to pull thread list explicitly, IIUC, so we
> can remove them. How about the patch below?
Thanks! I intended to do something like that myself after a period.
Looks good, please push.
Thanks,
Pedro Alves