This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [pushed][PATCH 6/7] Extended-remote fork catch
- From: Don Breazeal <donb at codesourcery dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>, "Breazeal, Don" <Don_Breazeal at mentor dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 14 May 2015 16:26:15 -0700
- Subject: Re: [pushed][PATCH 6/7] Extended-remote fork catch
- Authentication-results: sourceware.org; auth=none
- References: <1431451695-12273-1-git-send-email-donb at codesourcery dot com> <1431451695-12273-6-git-send-email-donb at codesourcery dot com> <87h9rehks0 dot fsf at redhat dot com>
On 5/14/2015 3:11 PM, Sergio Durigan Junior wrote:
> On Tuesday, May 12 2015, Don Breazeal wrote:
>
>> This is the version of the patch that I pushed.
>> Thanks
>> --Don
>
> Hi Don,
>
> I see a bunch of failures introduced by your patches on our BuildBot.
> For example, for this specific patch, I see:
>
> <https://sourceware.org/ml/gdb-testers/2015-q2/msg04109.html>
>
> This is on Debian, but I also see the failures on Fedora 21:
>
> <https://sourceware.org/ml/gdb-testers/2015-q2/msg04127.html>
>
> Are they expected?
>
Hi Sergio
The failures in gdb.base/foll-vfork.exp, gdb.base/multi-forks.exp, and
gdb.threads/fork-thread-pending.exp are not expected.
The failures in gdb.threads/interrupted-hand-call.exp and
gdb.gdb/python-selftest.exp are failures that I saw intermittently in my
testing, and was able to reproduce on the mainline, as discussed here:
https://sourceware.org/ml/gdb-patches/2015-05/msg00180.html
The failure in gdb.base/attach.exp I don't know...the log doesn't
provide any clues. I'll have to reproduce it to understand it.
Disappointing. I'll check out a clean sandbox and see if I can
reproduce any of these results.
--Don