Re: gdb crash when printing C++ class

Kris Warkentin
2004-12-10T21:44:54Z

I compared the vptr entries in the readelf -wi output from gcc vs. icc
and they're certainly different. I sent the gcc vs. icc output files to
Daniel directly - a little too big for the mailing list. If anyone else
wants them, let me know. My knowledge isn't deep enough to tell which
differences are significant.

I set a breakpoint in dwarf2read.c at the point where the vptr basetype
is set and what do you know? With the icc generated code, it's never
hit. I've got the dwarf-2 specification printed out here...I guess I'm
going to have to figure out what the heck a DIE is and all the other
stuff I wish I didn't need to know. ;-)

cheers,

Kris

Daniel Jacobowitz wrote:

>On Fri, Dec 10, 2004 at 03:03:35PM -0500, Kris Warkentin wrote:
>
>
>>Where was the vptr_basetype set up in the first place? Since type
>>
>>
>
>Take a look at the dwarf2 reader. TYPE_VPTR_BASETYPE.
>
>
>
>>claims to have a baseclass, logically the baseclass pointer shouldn't be
>>void so I'm assuming it just didn't get filled in somewhere. Can anyone
>>give me any hints on how to determine if Intel's debug info is off?
>>
>>
>
>It's probably not wrong, just different. Please show an example
>(readelf -wi will dump it).
>
>
>