From: Brian Ford <ford@vss.fsi.com>
To: gdb@sources.redhat.com
Subject: Re: DWARF2 PE/COFF port and parsing ?
Date: Tue, 20 May 2003 22:05:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0305201703090.22269-100000@eos> (raw)
In-Reply-To: <Pine.GSO.4.44.0305201641030.22269-100000@eos>
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'}
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next prev parent reply other threads:[~2003-05-20 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 21:15 Brian Ford
2003-05-20 21:34 ` David Carlton
2003-05-20 21:57 ` Brian Ford
2003-05-20 22:05 ` Brian Ford [this message]
2003-05-20 22:45 ` David Carlton
2003-05-20 22:17 ` David Carlton
[not found] <Pine.GSO.4.44.0305201745440.22269-100000@eos>
2003-05-20 23:09 ` Brian Ford
[not found] <vt2el2st5tj.fsf@zenia.red-bean.com>
2003-05-21 21:11 ` Brian Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.44.0305201703090.22269-100000@eos \
--to=ford@vss.fsi.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).