public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/11942] New: Duplicate type_hash when reloading debug info of dwarf4 signatured types. Date: Mon, 23 Aug 2010 21:18:00 -0000 [thread overview] Message-ID: <20100823211821.11942.dje@google.com> (raw) gdb version: When reloading debug information (e.g. because the info got freed due to max- cache-age), gdb can create a second type_hash table for a signatured type CU, and not reuse an existing table. This can be seen with the following patch: diff -u -p -r1.439 dwarf2read.c --- dwarf2read.c 20 Aug 2010 17:16:44 -0000 1.439 +++ dwarf2read.c 23 Aug 2010 21:12:13 -0000 @@ -14203,6 +14203,7 @@ set_die_type (struct die_info *die, stru if (cu->type_hash == NULL) { gdb_assert (cu->per_cu != NULL); + gdb_assert (cu->per_cu->type_hash == NULL); cu->per_cu->type_hash = htab_create_alloc_ex (cu->header.length / 24, offset_and_type_hash, -- Summary: Duplicate type_hash when reloading debug info of dwarf4 signatured types. Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: symtab AssignedTo: dje at google dot com ReportedBy: dje at google dot com CC: gdb-prs at sourceware dot org GCC host triplet: amd64-linux http://sourceware.org/bugzilla/show_bug.cgi?id=11942 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-08-23 21:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-23 21:18 dje at google dot com [this message] 2010-08-23 21:19 ` [Bug symtab/11942] " dje at google dot com 2010-08-23 21:20 ` dje at google dot com
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=20100823211821.11942.dje@google.com \ --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).