Re: Problems with breakpoints in constructors

["Amit S. Kale" <amitkale at linsyssoft dot com>]

Here they. There are two files dump.txt with my changes and dump.orig.txt 
without them.

I read the abbreviations related stuff from dwarf document. Also looked at the 
gcc code that  generates abbreviations. The gcc code looks correct.

Something is messed up in the dwarfdump utility output. I can't find correct 
abbreviations tags in debug_info. The dump_info records for 2 instances of 
MyClass and 1 instance of afun contain DW_AT_MIPS_linkage_name attribute. 
Both of them point to the same abbreviation entry. Yet when I debugged gdb's 
read_partial_die function, I found that the abbreviation entry for afun and 
MyClass is different. The afun entry contains 7 attributes, including 
DW_AT_MIPS_linkage_name and MyClass entry contains 6 attributes, without the 
MIPS entry.

How do I verify whether what dwarfdump output shows is incorrect or whether 
gdb's interpretation of the dwarf data is incorrect?

-Amit

On Wednesday 04 Aug 2004 9:06 pm, Daniel Jacobowitz wrote:
> On Wed, Aug 04, 2004 at 10:38:02AM +0530, Amit S. Kale wrote:
> > I believe I got DW_AT_MIPS_linkage_name in concrete instance by doing
> > this.
> >
> > I defined class as follows
> > class MyClass  { public:
> > 	MyClass(void);
> > 	void afun(void); };
> > MyClass::MyClass(void) { }
> > void MyClass::afun(void) { }
> >
> > This is followed by empty definitions for the two member functions.
> >
> > I got the mips linkage names in concrete definitions in .debug_info
> > section as shown by dwarfdump utility:
>
> Please show the entire output of dwarfdump before and after; I can't
> interpret these without more context.
>
> > Does .debug_abbrev contain abstract definitions?
>
> .debug_abbrev contains only templates for .debug_info.  You may wish to
> read the dwarf2 specification, which explains what they are.  In any
> case it is not an issue.

Attachment: dump.txt
Description: Text document

Attachment: dump.orig.txt
Description: Text document