Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jacques-Olivier Goussard <jgoussard@nuance.com>,
	gdb@sourceware.cygnus.com
Subject: Re: Helping GDB to find symbols
Date: Tue, 01 May 2001 01:44:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010501114557.29799B-100000@is> (raw)
In-Reply-To: <3AED9537.D7EBB9BD@cygnus.com>

On Mon, 30 Apr 2001, Andrew Cagney wrote:

> > 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.

In what way is this different from "gdb program core"?  If the
difference is important, I think the manual lacks an explanation of
that difference.


  reply	other threads:[~2001-05-01  1:44 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
2001-05-01  1:44   ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1010501114557.29799B-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=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