This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb can't handle a DIE with both sibling and children

From: David Carlton <carlton at kealia dot com>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: GDB <gdb at sources dot redhat dot com>
Date: Thu, 31 Jul 2003 13:29:22 -0700
Subject: Re: gdb can't handle a DIE with both sibling and children
References: <20030731181355.GA14242@lucon.org><20030731182049.GA20335@nevyn.them.org><yf24r12zdxs.fsf@hawaii.kealia.com> <20030731195640.GA16048@lucon.org><20030731200215.GA17805@nevyn.them.org><20030731202229.GA16545@lucon.org>

On Thu, 31 Jul 2003 13:22:29 -0700, "H. J. Lu" <hjl@lucon.org> said:

> See

> http://www-sld.slac.stanford.edu/HELP/FORTRAN/STATEMENTS/ENTRY

Blech.  Fortran is gross.  Yes, you'll have to modify
scan_partial_symbols.  I'm just glad that entries can't contain
DW_AT_specification; then we'd really be screwed.

David Carlton
carlton@kealia.com

References:
- gdb can't handle a DIE with both sibling and children
  - From: H. J. Lu
- Re: gdb can't handle a DIE with both sibling and children
  - From: Daniel Jacobowitz
- Re: gdb can't handle a DIE with both sibling and children
  - From: David Carlton
- Re: gdb can't handle a DIE with both sibling and children
  - From: H. J. Lu
- Re: gdb can't handle a DIE with both sibling and children
  - From: Daniel Jacobowitz
- Re: gdb can't handle a DIE with both sibling and children
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]