Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jaimon Jose <jjaimon@Yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: Reading symbols from dynamic symbol table
Date: Wed, 08 Dec 2004 04:46:00 -0000	[thread overview]
Message-ID: <20041208044558.GA2913@nevyn.them.org> (raw)
In-Reply-To: <41B68423.9080509@Yahoo.com>

On Wed, Dec 08, 2004 at 10:03:39AM +0530, Jaimon Jose wrote:
> I have few libraries built with --retain-symbols-file ld option.  I 
> can't see the correct symbols when I open the core file due to this. It 
> always shows the stack trace with few exported symbols+offset.  However, 
> 'nm' is able to read all the symbols from dynamic symbol table.  Is 
> there a way to instruct gdb to read symbols from dynamic symbol table?

It normally does - is this ELF?  You'll have to investigate why it
isn't working.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-12-08  4:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  4:33 Jaimon Jose
2004-12-08  4:46 ` Daniel Jacobowitz [this message]
2004-12-08  6:51   ` Jaimon Jose

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=20041208044558.GA2913@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jjaimon@Yahoo.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