This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: DWARF2 PE/COFF port and parsing ?
- From: David Carlton <carlton at math dot stanford dot edu>
- To: Brian Ford <ford at vss dot fsi dot com>
- Cc: gdb at sources dot redhat dot com
- Date: 20 May 2003 15:44:24 -0700
- Subject: Re: DWARF2 PE/COFF port and parsing ?
- References: <Pine.GSO.4.44.0305201703090.22269-100000@eos>
On Tue, 20 May 2003 17:05:26 -0500 (CDT), Brian Ford <ford@vss.fsi.com> said:
> On Tue, 20 May 2003, Brian Ford wrote:
>> > What does "p *pst" say? Unfortunately, the bug may have occurred when
>> > another psymtab was being generated: all the psymtabs within one
>> > objfile share one data structure, so an error when generating one
>> > psymtab may corrupt another psymtab's data. (Sigh. Partial symbol
>> > tables are a mess.)
>> >
>> (gdb) p *pst
>> Cannot access memory at address 0x0
>> (gdb) p pst
>> $1 = (struct partial_symtab *) 0x0
>>
> Um, sorry. That obviously looks wrong because of optimization. Here is
> what it says without -O2:
> (gdb) p *pst
> $1 = {next = 0x1052a018, filename = 0x1052a0e8 "../../gcc/gcc/libgcc2.c",
> fullname = 0x0, objfile = 0x10148238, section_offsets = 0x1014e440,
> textlow = 4922848, texthigh = 4922848, dependencies = 0x1052a118,
> number_of_dependencies = 4, globals_offset = 1151, n_global_syms = 2,
> statics_offset = 24280, n_static_syms = 21, symtab = 0x0,
> read_symtab = 0x4f1170 <dbx_psymtab_to_symtab>,
> read_symtab_private = 0x1052a100 "D\030\031", readin = 0 '\0'}
Hmm. It doesn't look too strange to me. Are the libraries that GCC
builds being compiled using your DWARF 2 in PE/COFF mechanisms? If
not, is there any way you can think of that that would cause problems?
David Carlton
carlton@math.stanford.edu