From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Don Breazeal <donb@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [pushed][PATCH 6/7] Extended-remote fork catch
Date: Thu, 14 May 2015 22:11:00 -0000 [thread overview]
Message-ID: <87h9rehks0.fsf@redhat.com> (raw)
In-Reply-To: <1431451695-12273-6-git-send-email-donb@codesourcery.com> (Don Breazeal's message of "Tue, 12 May 2015 10:28:14 -0700")
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?
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-05-14 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 17:28 [pushed][PATCH 1/7] Identify remote fork event support Don Breazeal
2015-05-12 17:28 ` [pushed][PATCH 3/7] Extended-remote Linux follow fork Don Breazeal
2015-05-12 17:28 ` [pushed][PATCH 2/7] Clone remote breakpoints Don Breazeal
2015-05-12 17:29 ` [pushed][PATCH 5/7] Extended-remote follow vfork Don Breazeal
2015-05-12 17:29 ` [pushed][PATCH 4/7] Arch-specific remote follow fork Don Breazeal
2015-05-14 10:25 ` Vidya Praveen
2015-05-14 16:02 ` Breazeal, Don
2015-05-12 17:29 ` [pushed][PATCH 7/7] Extended-remote fork event docs Don Breazeal
2015-05-12 17:29 ` [pushed][PATCH 6/7] Extended-remote fork catch Don Breazeal
2015-05-14 22:11 ` Sergio Durigan Junior [this message]
2015-05-14 23:26 ` Don Breazeal
2015-05-14 23:41 ` Sergio Durigan Junior
2015-05-28 22:22 ` Don Breazeal
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=87h9rehks0.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=donb@codesourcery.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