From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7657 invoked by alias); 10 Dec 2004 21:44:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7630 invoked from network); 10 Dec 2004 21:44:51 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sourceware.org with SMTP; 10 Dec 2004 21:44:51 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id RAA22039 for ; Fri, 10 Dec 2004 17:05:32 -0500 Received: from [10.12.1.181] (dhcpa181 [10.12.1.181]) by smtp.ott.qnx.com (8.8.8/8.6.12) with ESMTP id QAA12716 for ; Fri, 10 Dec 2004 16:44:51 -0500 Message-ID: <41BA1978.1040509@qnx.com> Date: Fri, 10 Dec 2004 21:44:00 -0000 From: Kris Warkentin User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Re: gdb crash when printing C++ class References: <41BA0117.40407@qnx.com> <20041210202108.GA7717@nevyn.them.org> In-Reply-To: <20041210202108.GA7717@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00076.txt.bz2 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). > > >