Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: New UNRESOLVED testcase gdb.dwarf2/dw2-double-set-die-type.exp  [Re: [RFA] Delayed physnames, revisited]
Date: Mon, 23 Aug 2010 19:13:00 -0000	[thread overview]
Message-ID: <4C72C834.7060803@redhat.com> (raw)
In-Reply-To: <20100822184631.GA28572@host1.dyn.jankratochvil.net>

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On 08/22/2010 11:46 AM, Jan Kratochvil wrote:
> There is one missing end-of-DIE-children at the end of .debug_info.  But I do
> not know which specific DIE is not terminated before it.

Yes, there was. Turns out there were two *similar* abbrevs in the 
original program. I missed that one of them was marked DW_children_no 
and the other DW_children_yes. Creating a new abbrev with DW_children_no 
and using that fixes the problem.

>
> Also .debug_abbrev seems to be missing its terminating entry.

Yup. I've added that, too.

I've checked this in as obvious (and I have verified with Jan that 
everything now works).

Keith

ChangeLog
2010-08-23  Keith Seitz  <keiths@redhat.com>

	* gdb.dwarf2/dw2-double-set-die-type.S: DIE 0x51f does not
	have any children. Create a new abbrev for it.
	Add missing terminal sequence to .debug_abbrev.


[-- Attachment #2: double-die-no-children.patch --]
[-- Type: text/plain, Size: 1270 bytes --]

Index: testsuite/gdb.dwarf2/dw2-double-set-die-type.S
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.dwarf2/dw2-double-set-die-type.S,v
retrieving revision 1.1
diff -u -p -r1.1 dw2-double-set-die-type.S
--- testsuite/gdb.dwarf2/dw2-double-set-die-type.S	20 Aug 2010 17:16:15 -0000	1.1
+++ testsuite/gdb.dwarf2/dw2-double-set-die-type.S	23 Aug 2010 19:11:48 -0000
@@ -282,7 +282,7 @@
 	.byte	0x0	# end of children of DIE 0x505
 
 .Ldie_51f:
-	.uleb128 0x21	# (DIE (0x51f) DW_TAG_subprogram)
+	.uleb128 0x23	# (DIE (0x51f) DW_TAG_subprogram)
 	.byte	0x1	# DW_AT_external
 	.ascii	"_M_allocate\0"	# DW_AT_name
 	.long	OFFSET (277)	# DW_AT_type
@@ -630,3 +630,23 @@
 	.uleb128 0x13	# (DW_FORM_ref4)
 	.byte	0x0
 	.byte	0x0
+
+	.uleb128 0x23	# (abbrev code)
+	.uleb128 0x2e	# (TAG: DW_TAG_subprogram)
+	.byte	0x0	# DW_children_no
+	.uleb128 0x3f	# (DW_AT_external)
+	.uleb128 0xc	# (DW_FORM_flag)
+	.uleb128 0x3	# (DW_AT_name)
+	.uleb128 0x8	# (DW_FORM_string)
+	.uleb128 0x49	# (DW_AT_type)
+	.uleb128 0x13	# (DW_FORM_ref4)
+	.uleb128 0x3c	# (DW_AT_declaration)
+	.uleb128 0xc	# (DW_FORM_flag)
+	.uleb128 0x1	# (DW_AT_sibling)
+	.uleb128 0x13	# (DW_FORM_ref4)
+	.byte	0x0
+	.byte	0x0
+
+	.byte	0x0
+	.byte	0x0
+

  reply	other threads:[~2010-08-23 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 21:01 [RFA] Delayed physnames, revisited Keith Seitz
2010-08-19 19:36 ` Tom Tromey
2010-08-19 23:26   ` Doug Evans
2010-08-20 17:17     ` Keith Seitz
2010-08-22 18:46       ` New UNRESOLVED testcase gdb.dwarf2/dw2-double-set-die-type.exp [Re: [RFA] Delayed physnames, revisited] Jan Kratochvil
2010-08-23 19:13         ` Keith Seitz [this message]
2010-08-20 17:50     ` [RFA] Delayed physnames, revisited Thiago Jung Bauermann

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=4C72C834.7060803@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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