Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gaius Mulley <gaius@glam.ac.uk>
To: gdb-patches@sourceware.org
Cc: drow@false.org
Subject: Re: recursive bug in dwarf2read.c
Date: Thu, 10 Dec 2009 19:39:00 -0000	[thread overview]
Message-ID: <87pr6mliuh.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <20091209185157.GA29691@caradoc.them.org> (Daniel Jacobowitz's message of "Wed\, 9 Dec 2009 13\:51\:57 -0500")


Daniel Jacobowitz <drow@false.org> writes:

> On Wed, Dec 09, 2009 at 10:55:30AM +0000, Gaius Mulley wrote:
>> 
>> Hi,
>> 
>> I think there is a bug in dwarf2read.c which can be exposed by
>> attempting to set a break point at RealIO_WriteFixed in this
>> executable.
>> 
>> I acknowledge the (gnu modula-2 generated executable) could probably
>> be at fault, nevertheless it does contain cyclic data structures which
>> are not explicitly created in the same way as C.  For example:
>> 
>> 
>> TYPE
>>   ScanState =  PROCEDURE (CHAR, VAR ScanClass, VAR ScanState);
>
> See e.g. this from read_structure_type:
>
>   /* We need to add the type field to the die immediately so we don't
>      infinitely recurse when dealing with pointers to the structure
>      type within the structure itself. */
>   set_die_type (die, type, cu);
>
> It looks as if read_subroutine_type does not do that, but now has to.

Hi Daniel,

here is a patch which fixes the bug above.  Embarrassingly after
checking my private gdb directories I found I fixed this last year
and sat on and forgot the patch.  Guess there is a moral here
somewhere..


2009-12-10  Gaius Mulley  <gaius@glam.ac.uk>

	* dwarf2read.c (read_subroutine_type): Add the subroutine
	  type to the die immediately to allow a parameter type to be
	  the same subroutine type.


--- src-orig/gdb/dwarf2read.c	2009-12-10 16:41:40.000000000 +0000
+++ src/gdb/dwarf2read.c	2009-12-10 17:04:16.000000000 +0000
@@ -5879,6 +5879,11 @@
      the default value DW_CC_normal.  */
   attr = dwarf2_attr (die, DW_AT_calling_convention, cu);
   TYPE_CALLING_CONVENTION (ftype) = attr ? DW_UNSND (attr) : DW_CC_normal;
+
+  /* We need to add the subroutine type to the die immediately so
+     we don't infinitely recurse when dealing with parameters
+     declared as the same subroutine type. */
+  set_die_type (die, ftype, cu);
   
   if (die->child != NULL)
     {


I've ran the testsuite on a AMD64 debian stable (lenny) system and and
it doesn't appear to cause any regression.  I've also some minor
Modula-2 language support improvement patches which I wrote in Sept
which I'll now push out to the mailing list..

regards,
Gaius


       reply	other threads:[~2009-12-10 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878wdcto0t.fsf@j228-gm.comp.glam.ac.uk>
     [not found] ` <20091209185157.GA29691@caradoc.them.org>
2009-12-10 19:39   ` Gaius Mulley [this message]
2009-12-11 19:29     ` Tom Tromey
2009-12-11 20:56       ` Gaius Mulley
2009-12-11 21:06         ` Tom Tromey
2009-12-16 15:14           ` Gaius Mulley

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=87pr6mliuh.fsf@j228-gm.comp.glam.ac.uk \
    --to=gaius@glam.ac.uk \
    --cc=drow@false.org \
    --cc=gdb-patches@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