From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24
Date: Wed, 29 Aug 2018 21:33:00 -0000 [thread overview]
Message-ID: <87bm9kx3ht.fsf@tromey.com> (raw)
In-Reply-To: <87a7p4lx9u.fsf@redhat.com> (Sergio Durigan Junior's message of "Wed, 29 Aug 2018 16:42:53 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> After my last commit, which updated GDB's local copy of gnulib, I'm
Sergio> seeing a breakage on the RHEL 7.1 s390x builder (see the rest of the
Sergio> quoted message). Unfortunately I don't have easy access to a similar
Sergio> machine, so I would like to know if:
Something fishy is going on that builder. I did a try run of my ubsan
series and got many errors like this:
(gdb) break check_vx
/usr/include/c++/4.8.2/debug/vector:
Error: attempt to subscript container with out-of-bounds index gdb: /home/dje/src/gcc-6-branch/libstdc++-v3/src/c++11/debug.cc:942: void {anonymous}::print_string({anonymous}::PrintContext&, const char*, const _Parameter*, std::size_t): Assertion `param_index < num_parameters' failed.
However I think this should only happen if libstdc++ debug mode is
enabled. (Is this correct? Maybe this is the error.)
I did do some try runs in the past of libstdc++ debug mode. So, I am
wondering if there could somehow be stale .o files around. I don't see
how really -- I'd expect configure to make config.h, and for that to
force a full rebuild. But it still looks suspicious.
Tom
next prev parent reply other threads:[~2018-08-29 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:31 Oh dear. I regret to inform you that commit 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 might be unfortunate gdb-buildbot
2018-08-29 16:31 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 gdb-buildbot
2018-08-29 16:39 ` Sergio Durigan Junior
2018-08-29 20:42 ` Sergio Durigan Junior
2018-08-29 21:33 ` Tom Tromey [this message]
2018-08-29 21:37 ` Sergio Durigan Junior
2018-08-30 0:50 ` Tom Tromey
2018-08-30 3:04 ` Sergio Durigan Junior
2018-09-01 0:01 ` Tom Tromey
2018-09-03 10:04 ` Jonah Graham
2018-09-04 0:46 ` Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24) Sergio Durigan Junior
2018-09-04 6:20 ` Jonah Graham
2018-09-04 18:04 ` Proposal to revert the gnulib update patch Sergio Durigan Junior
2018-09-04 18:09 ` Tom Tromey
2018-08-30 3:06 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 Sergio Durigan Junior
2018-08-30 1:55 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2018-08-30 1:57 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-08-30 1:58 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
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=87bm9kx3ht.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
/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).