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] PR symtab/17391 gdb internal error: assertion fails in regcache.c:178 Date: Mon, 26 Oct 2015 23:16:00 -0000 [thread overview] Message-ID: <0fde2c536bc483baa4baa2990ebebfb3a7c00415@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 0fde2c536bc483baa4baa2990ebebfb3a7c00415 *** Author: Doug Evans <dje@google.com> Branch: master Commit: 0fde2c536bc483baa4baa2990ebebfb3a7c00415 PR symtab/17391 gdb internal error: assertion fails in regcache.c:178 gdb/ChangeLog: * dwarf2-frame.c (dwarf2_restore_rule): Call dwarf_reg_to_regnum instead of gdbarch_dwarf2_reg_to_regnum. (dwarf2_frame_cache): Ditto. (read_addr_from_reg): Call dwarf_reg_to_regnum_or_error instead of gdbarch_dwarf2_reg_to_regnum. (get_reg_value): Ditto. (dwarf2_fetch_cfa_info): Ditto. (dwarf2_frame_prev_register): Ditto. * dwarf2loc.c: #include "complaints.h". (dwarf_expr_read_addr_from_reg): Call dwarf_reg_to_regnum_or_error instead of gdbarch_dwarf2_reg_to_regnum. (dwarf_expr_get_reg_value): Ditto. (read_pieced_value): Ditto. (write_pieced_value): Ditto. (dwarf2_evaluate_loc_desc_full): Ditto. (dwarf_reg_to_regnum): New function. (throw_bad_regnum_error): New function. (dwarf_reg_to_regnum_or_error): Renamed from dwarf2_reg_to_regnum_or_errorChange to take a ULONGEST regnum. All callers updated. Call throw_bad_regnum_error. (locexpr_regname): Improve text of bad register number. * dwarf2loc.h (dwarf_reg_to_regnum): Declare. (dwarf_reg_to_regnum_or_error): Update prototype. * dwarf2expr.c: #include "dwarf2loc.h". (dwarf_block_to_sp_offset): Call dwarf_reg_to_regnum instead of gdbarch_dwarf2_reg_to_regnum. * gdbarch.sh (dwarf2_reg_to_regnum): Add comment. * gdbarch.h: Regenerate. * amd64-tdep.c (amd64_dwarf_reg_to_regnum): Remove warning for bad register. * avr-tdep.c (avr_dwarf_reg_to_regnum): Ditto. * cris-tdep.c (cris_dwarf2_reg_to_regnum): Ditto. * bfin-tdep.c (bfin_reg_to_regnum): Fix error checking. * hppa-linux-tdep.c (hppa_dwarf_reg_to_regnum): Improve error checking. Remove warning for bad register. * hppa-tdep.c (hppa64_dwarf_reg_to_regnum): Ditto. * i386-tdep.c (i386_svr4_dwarf_reg_to_regnum): Renamed from i386_svr4_reg_to_regnum. Return -1 for bad registers. (i386_svr4_reg_to_regnum): New function. (i386_gdbarch_init): Update call to set_gdbarch_dwarf2_reg_to_regnum. * microblaze-tdep.c (microblaze_dwarf2_reg_to_regnum): Don't assert on bad registers, return -1. * msp430-tdep.c (msp430_dwarf2_reg_to_regnum): Improve error checking. Remove warning for bad register. * nios2-tdep.c: Add static assert for NIOS2_NUM_REGS. (nios2_dwarf_reg_to_regnum): Fix off-by-one error. Remove warning for bad register. Return -1 for bad register. * rl78-tdep.c (rl78_dwarf_reg_to_regnum): Don't flag an internal error for bad register, return -1. * rx-tdep.c (rx_dwarf_reg_to_regnum): Ditto. * m68k-tdep.c (m68k_dwarf_reg_to_regnum): Fix error result. * mep-tdep.c (mep_debug_reg_to_regnum): Ditto. * mips-tdep.c (mips_stab_reg_to_regnum): Ditto. (mips_dwarf_dwarf2_ecoff_reg_to_regnum): Ditto. * mn10300-tdep.c (mn10300_dwarf2_reg_to_regnum): Remove warning for bad regs. * xtensa-tdep.c (xtensa_reg_to_regnum): Remove internal error for bad regs. Fix error result. * stabsread.c (stab_reg_to_regnum): Watch for negative regno. (reg_value_complaint): Update complaint text. * mdebugread.c (reg_value_complaint): New function. (mdebug_reg_to_regnum): Rewrite to watch for bad reg numbers. gdb/testsuite/ChangeLog: * lib/dwarf.exp (_location): Add support for DW_OP_regx. * gdb.dwarf2/bad-regnum.c: New file. * gdb.dwarf2/bad-regnum.exp: New file.
next reply other threads:[~2015-10-26 23:16 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-26 23:16 sergiodj+buildbot [this message] 2015-10-26 23:17 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot 2015-10-26 23:17 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2015-10-26 23:33 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-10-26 23:33 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2015-10-27 1:21 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-10-27 1:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-10-27 1:42 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-10-27 1:55 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2015-10-27 2:02 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-10-27 3:29 ` Failures on Debian-i686, " sergiodj+buildbot 2015-10-27 3:50 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-10-27 4:57 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-10-27 6:31 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-10-27 6:54 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-10-27 7:11 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-10-27 7:28 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-10-27 11:15 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-10-27 11:32 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-10-27 11:43 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-10-27 12:02 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot 2015-10-27 13:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " 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=0fde2c536bc483baa4baa2990ebebfb3a7c00415@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).