From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao.qi@linaro.org>
Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate
Date: Sun, 10 Sep 2017 05:54:00 -0000 [thread overview]
Message-ID: <87r2vfp08q.fsf@redhat.com> (raw)
In-Reply-To: <87lglqtk8j.fsf@redhat.com> (Sergio Durigan Junior's message of "Thu, 07 Sep 2017 14:51:56 -0400")
On Thursday, September 07 2017, I wrote:
> On Thursday, September 07 2017, Palmer Dabbelt wrote:
>
>> I think this wasn't my commits, as it seems to be broken as of 63c99141deff
>> ("remove QStartupWithShell entry from NEWS::Changes in GDB 7.11"). Also, I
>> haven't touched anything in aarch64 GDB land
>>
>> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2745
>>
>> I can't find any other mention of this on "gdb-patches", though I'm not a GDB
>> maintainer (we don't have a RISC-V GDB port yet) so I had to poke around the
>> archives and therefor may be missing something. According to here
>>
>> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64?numbuilds=400
>>
>> This has been broken since 34d16ea2a144 ("gdb.base/commands.exp: Test
>> loop_break and loop_continue in nested loops"), but that failure isn't relevant
>> to this one as it's a test failure not a build failure.
>>
>> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2671
>>
>> I poked around and there was at least one compilation failure in
>> between the one I just got emailed about and the test failure above, caused by
>> 7022349d5c86 ("Stop assuming no-debug-info functions return int").
>>
>> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2673/steps/compile%20gdb/logs/stdio
>>
>> Given that there's two different failures in three commits and I'm pretty sure
>> I didn't cause this bug, I don't want to dig through the rest of the history to
>> figure out what's going on. This has been broken for a while, is everyone else
>> just ignoring these messages?
>
> Hi Palmer,
>
> Thanks for investigating these issues.
>
> There's been a bunch of compilation errors on this builder,
> unfortunately. The last one is caused by commit
> f7000548a2b79d7e5cb924468117ca4245e6b820, from Yao.
>
> Yao, could you please take a look at the error? You can see the build
> logs here:
>
> https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2696/steps/compile%20gdb/logs/stdio
FWIW, I sent a patch that fixes this:
<https://sourceware.org/ml/gdb-patches/2017-09/msg00264.html>
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2017-09-10 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dq0Uz-00056v-Ti@kwanyin.sergiodj.net>
2017-09-07 17:56 ` Palmer Dabbelt
2017-09-07 18:00 ` H.J. Lu
2017-09-07 18:57 ` Sergio Durigan Junior
2017-09-07 19:32 ` H.J. Lu
2017-09-07 19:41 ` Sergio Durigan Junior
2017-09-07 19:52 ` H.J. Lu
2017-09-07 19:54 ` Sergio Durigan Junior
2017-09-07 19:57 ` Sergio Durigan Junior
2017-09-07 23:35 ` Joel Brobecker
2017-09-08 2:10 ` H.J. Lu
2017-09-08 5:41 ` Sergio Durigan Junior
2017-09-07 18:52 ` Sergio Durigan Junior
2017-09-10 5:54 ` Sergio Durigan Junior [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=87r2vfp08q.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.com \
--cc=yao.qi@linaro.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