From: Brian Ford <ford@vss.fsi.com>
To: gdb@sources.redhat.com
Subject: Re: DWARF2 PE/COFF port and parsing ?
Date: Wed, 21 May 2003 21:11:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0305211608560.8236-100000@eos> (raw)
In-Reply-To: <vt2el2st5tj.fsf@zenia.red-bean.com>
On 21 May 2003, Jim Blandy wrote:
> You may find the 'maint info psymtab' and 'maint info symtab'
> functions helpful in debugging this kind of thing. The output
> includes addresses for the objects it describes.
>
Thanks. The problem is, I crash as soon as I load the symbol file while
looking up main. So, the command interface isn't very helpful.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next parent reply other threads:[~2003-05-21 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vt2el2st5tj.fsf@zenia.red-bean.com>
2003-05-21 21:11 ` Brian Ford [this message]
[not found] <Pine.GSO.4.44.0305201745440.22269-100000@eos>
2003-05-20 23:09 ` Brian Ford
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
2003-05-20 22:45 ` David Carlton
2003-05-20 22:17 ` David Carlton
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.0305211608560.8236-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