From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: gdb@sourceware.org
Subject: Re: Array out of bounds
Date: Tue, 7 Sep 2021 10:27:03 -0400 [thread overview]
Message-ID: <ea8d8558-d47b-10fb-ff54-327f6eb24949@polymtl.ca> (raw)
In-Reply-To: <20210906060302.wltmsjzf6aadsg3e@lug-owl.de>
On 2021-09-06 2:03 a.m., Jan-Benedict Glaw wrote:
> Hi!
>
> On Sun, 2021-09-05 21:48:22 -0400, Simon Marchi <simon.marchi@polymtl.ca> wrote:
>> On 2021-09-05 2:06 p.m., Jan-Benedict Glaw wrote:
>>> On Sun, 2021-09-05 08:40:35 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>>>> Hi!
>>>>
>>>> As I started with automated building/testing the GNU Toolchain again,
>>>> I found this when building GDB (make all-gdb) with a fairly recent GCC
>>>> on a Linux system (PC) when GDB is configured for
>>>> --target=aarch64-linux:
>>>
>>> Just to add: Seems to be independent of a target. Produces the same
>>> warning/error for all tested targets using a current GCC.
>>
>> I just built gcc at 66bba4dc263d ("Daily bump."), and I don't see it.
>
> For which target did you build? I actually don't see it for a small
> number, ie:
> * xtensa-linux
> * fr30-elf
> * hppa2.0-hpux11.9
> * hppa64-hpux
> * hppa64-hpux11.0
> * hppa64-hpux11.3
> * ia64-elf
> * ia64-hpux
> * mmix-knuth-mmixware
> * powerpc-darwin7
> * pdp11-aout
> * powerpc-darwin8
> * s390x-ibm-tpf
> * x86_64-apple-darwin
>
> Maybe you had a lucky pick? Only IPv6 connectivity at the moment, but
> here are a few (failed) build logs for more common targets:
>
> http://wolf.lug-owl.de:8080/jobs/gdb-alpha-netbsd/6
> http://wolf.lug-owl.de:8080/jobs/gdb-m68k-linux/6
> http://wolf.lug-owl.de:8080/jobs/gdb-mips-linux/6
> http://wolf.lug-owl.de:8080/jobs/gdb-powerpc-linux/6
> http://wolf.lug-owl.de:8080/jobs/gdb-x86_64-linux/6
>
> MfG, JBG
Since the failure is in language.c, the target should not matter, as
language.c is compiled the same way whatever the target. Anyway, seems
like Tom managed to reproduce it and filed a gcc bug, thanks Tom!
Simon
next prev parent reply other threads:[~2021-09-07 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 6:40 Jan-Benedict Glaw
2021-09-05 18:06 ` Jan-Benedict Glaw
2021-09-06 1:48 ` Simon Marchi
2021-09-06 6:03 ` Jan-Benedict Glaw
2021-09-07 14:27 ` Simon Marchi [this message]
2021-09-06 10:24 ` Tom de Vries
2021-09-06 14:49 ` Tom de Vries
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=ea8d8558-d47b-10fb-ff54-327f6eb24949@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=jbglaw@lug-owl.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).