From: Andrew Cagney <ac131313@cygnus.com>
To: Jacques-Olivier Goussard <jgoussard@nuance.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Helping GDB to find symbols
Date: Mon, 30 Apr 2001 09:39:00 -0000 [thread overview]
Message-ID: <3AED9537.D7EBB9BD@cygnus.com> (raw)
In-Reply-To: <NEBBKPBKLKFJPDFPMBDIAEPOCBAA.jgoussard@nuance.com>
Jacques-Olivier Goussard wrote:
>
> Hi all
> I hope that the proper list to send this...
> I have the following pb: I shipp products with no debug information,
> so when a customer has a core dump, I need to fall back on assembly
> output to try to tackle the pb.
> As I have access to the source code and the debug-compiled product,
> I was wondering if there was a mean to *help* GDB and provide it with
> some of the debug info.
> For ex, let say the prg crashed in function A, then GDB should be able
> to calculate the address of the args to A in the non-debug core. Then,
> finding the function in the debug-compiled library (may be with a little
> help), it should be able to load the defs of the args and show the values
> of each args properly.
> Is there a way to do that, or is this an enhancement to be added or is it
> a totally new idea that nobody thought about before (unlikely I guess) ?
> May be it can not be done ?
Check the command ``symbol-file'' in the user documentation. It should
do exactly what you want.
Andrew
next prev parent reply other threads:[~2001-04-30 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 9:16 Jacques-Olivier Goussard
2001-04-30 9:24 ` Eli Zaretskii
2001-04-30 9:32 ` Jacques-Olivier Goussard
2001-05-01 1:44 ` Eli Zaretskii
2001-05-01 6:05 ` Jacques-Olivier Goussard
2001-05-01 11:23 ` Eli Zaretskii
2001-05-01 12:19 ` Daniel Berlin
2001-05-01 9:54 ` Daniel Berlin
2001-04-30 9:39 ` Andrew Cagney [this message]
2001-05-01 1:44 ` Eli Zaretskii
2001-05-01 9:41 ` Andrew Cagney
2001-05-01 6:20 Nicolas.Thery
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=3AED9537.D7EBB9BD@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jgoussard@nuance.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