public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Issue complaint instead of assert for invalid/unhandled DW_AT_accessibility
Date: Wed, 18 Oct 2017 18:20:00 -0000 [thread overview]
Message-ID: <3753468682a9c7982b6eba0fca58fbfc1cd5b9fb@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 3753468682a9c7982b6eba0fca58fbfc1cd5b9fb ***
Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 3753468682a9c7982b6eba0fca58fbfc1cd5b9fb
Issue complaint instead of assert for invalid/unhandled DW_AT_accessibility
A previous patch called gdb_assert_not_reached whenever reading
the accessibility of a nested typedef definition. Wisely, Pedro has asked me
not do this.
This patch changes the previous one so that it issues a complaint instead.
gdb/ChangeLog:
* dwarf2read.c (dwarf2_add_typedef): Issue a complaint on unhandled
DW_AT_accessibility.
next reply other threads:[~2017-10-18 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 18:20 sergiodj+buildbot [this message]
2017-10-18 18:20 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2017-10-18 18:30 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-18 18:33 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-10-18 18:44 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-20 14:03 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-10-20 14:22 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-20 15:06 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-20 15:17 ` Failures on Fedora-x86_64-cc-with-index, " 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=3753468682a9c7982b6eba0fca58fbfc1cd5b9fb@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--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: 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).