public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb/gdb-7.10-branch] compile: Warn for old GCC on cv-qualified self-reference Date: Wed, 08 Jul 2015 13:27:00 -0000 [thread overview] Message-ID: <91affdd27ee8e244df417686ead2b546ee1449bf@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 91affdd27ee8e244df417686ead2b546ee1449bf *** Author: Jan Kratochvil <jan.kratochvil@redhat.com> Branch: gdb-7.10-branch Commit: 91affdd27ee8e244df417686ead2b546ee1449bf compile: Warn for old GCC on cv-qualified self-reference GDB could: compile code struct_object.selffield = &struct_object ./compile/compile-c-types.c:83: internal-error: insert_type: Assertion `add == NULL || add->gcc_type == gcc_type' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.compile/compile.exp: compile code struct_object.selffield = &struct_object (GDB internal error) The bug was not in GDB but in the GCC part interfacing with GDB. Alexandre Oliva has fixed it the right way: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=commitdiff;h=072dfdba0ea62abb65514cb3a90cdf3868efe286 git://gcc.gnu.org/git/gcc.git aoliva/libcp1 Attaching this GDB testsuite update + info to user s/he should upgrade GCC. After Alex upstreams the fix I can update the message to contain the specific GCC release. gdb/ChangeLog 2015-07-08 Jan Kratochvil <jan.kratochvil@redhat.com> PR compile/18484 * compile/compile-c-types.c (insert_type): Change gdb_assert to error. gdb/testsuite/ChangeLog 2015-07-08 Jan Kratochvil <jan.kratochvil@redhat.com> PR compile/18484 * gdb.compile/compile.c (struct struct_type): Add volatile to selffield's type. * gdb.compile/compile.exp (compile code struct_object.selffield = &struct_object): Skip further struct_object tests if this one xfails.
next reply other threads:[~2015-07-08 13:27 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-08 13:27 sergiodj+buildbot [this message] 2015-07-08 13:27 ` Failures on AIX-POWER7-plain, branch gdb-7.10-branch sergiodj+buildbot 2015-07-08 13:49 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2015-07-08 14:03 ` Failures on Debian-i686, " sergiodj+buildbot 2015-07-08 14:18 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2015-07-08 14:20 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-07-08 14:44 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-07-08 15:16 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-07-08 15:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-07-08 15:38 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-07-08 15:55 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-07-08 16:18 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-07-08 16:52 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-07-08 17:12 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-07-08 17:47 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2015-07-09 3:30 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-07-09 4:25 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-07-09 4:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-07-09 5:43 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+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=91affdd27ee8e244df417686ead2b546ee1449bf@gdb-build \ --to=sergiodj+buildbot@redhat.com \ --cc=gdb-testers@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: linkBe 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).