public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/17136] 'info type-printers' causes an exception when there are per-objfile printers Date: Thu, 24 Jul 2014 17:17:00 -0000 [thread overview] Message-ID: <bug-17136-4717-wKpk6s6FRL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17136-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17136 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz <keiths at redhat dot com> --- I am unable to reproduce this with either 7.7.1.20140611-cvs or git HEAD. What does your gdb report as its version? Example of my attempt to reproduce: $ ./gdb -q -data-directory data-directory gdb Reading symbols from gdb...done. Setting up the environment for debugging gdb. Breakpoint 1 at 0x6f6390: file ../../src/gdb/utils.c, line 829. Breakpoint 2 at 0x4ead77: file ../../src/gdb/cli/cli-cmds.c, line 219. (top-gdb) start Temporary breakpoint 3 at 0x45bdff: file ../../src/gdb/gdb.c, line 29. Starting program: /home/keiths/sources/gdb/git/releases/7.7/linux/gdb/gdb During symbol reading, cannot get low and high bounds for subprogram DIE at 8088. During symbol reading, Child DIE 0x31a3 and its abstract origin 0x684d have different tags. During symbol reading, Child DIE 0x31a3 and its abstract origin 0x684d have different parents. During symbol reading, DW_AT_GNU_call_site_target target DIE has invalid low pc, for referencing DIE 0x4961 [in module /usr/lib/debug/lib64/ld-2.18.so.debug]. During symbol reading, Multiple children of DIE 0x6253 refer to DIE 0x5df3 as their abstract origin. During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x3878e0397a. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x3878e0397a. Temporary breakpoint 3, main (argc=1, argv=0x7fffffffdce8) at ../../src/gdb/gdb.c:29 29 memset (&args, 0, sizeof args); (top-gdb) py execfile('/home/keiths/tmp/17136.py') (top-gdb) py gdb.types.register_type_printer (gdb.current_objfile(), Printer()) (top-gdb) info type-printers Global type printers: Printer (top-gdb) Do you have a different procedure which tickles the bug? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-24 17:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-09 12:08 [Bug python/17136] New: " jwakely.gcc at gmail dot com 2014-07-22 18:27 ` [Bug python/17136] " jan.kratochvil at redhat dot com 2014-07-24 17:17 ` keiths at redhat dot com [this message] 2015-05-29 12:06 ` jwakely.gcc at gmail dot com 2015-05-29 12:11 ` jwakely.gcc at gmail dot com 2015-06-01 19:02 ` dje at google dot com 2015-06-01 19:13 ` dje at google dot com 2015-06-01 19:22 ` dje at google dot com 2015-06-26 13:49 ` jan.kratochvil at redhat dot com 2015-08-06 16:26 ` cvs-commit at gcc dot gnu.org 2015-08-06 16:30 ` cvs-commit at gcc dot gnu.org 2015-08-06 16:35 ` dje at google dot com 2023-03-13 13:41 ` cvs-commit at gcc dot gnu.org
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=bug-17136-4717-wKpk6s6FRL@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).