From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29185 invoked by alias); 20 May 2003 22:17:27 -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 29147 invoked from network); 20 May 2003 22:17:26 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by sources.redhat.com with SMTP; 20 May 2003 22:17:26 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h4KMHM313985; Tue, 20 May 2003 15:17:22 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Brian Ford Cc: gdb@sources.redhat.com Subject: Re: DWARF2 PE/COFF port and parsing ? References: From: David Carlton Date: Tue, 20 May 2003 22:17:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg00281.txt.bz2 On Tue, 20 May 2003 16:56:52 -0500 (CDT), Brian Ford said: >> What does "p *pst" say? > (gdb) p *pst > Cannot access memory at address 0x0 > (gdb) p pst > $1 = (struct partial_symtab *) 0x0 That's unfortunate; maybe the optimizer has already invalidated pst at that point? You could try finding an earlier place in the command where pst is still valid and have GDB print out the value of pst each time it hits that location (which will happen a lot), and then, when GDB crashes, look at the last value for pst and print out *((struct partial_sytmab *) ) Maybe that will give a clue as to what's going on; maybe it won't. >> If this doesn't help, maybe you could give some more details about >> exactly how you've been tinkering with the readers. > Actually, I haven't. The tinkering I have done is in binutils to get > valid DWARF2 objects and let bfd know that PE/COFF can produce them. gdb > is current cvs. I have more tinkering to go, but the objects and > executables should be valid. libdwarf and dwarfdump have no trouble > parsing them. Weird. I'm pretty confused, but maybe following through the psymtab building will help. David Carlton carlton@math.stanford.edu