Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Unknown files
Date: Tue, 09 May 2006 14:30:00 -0000	[thread overview]
Message-ID: <4460A544.8060808@netspace.net.au> (raw)
In-Reply-To: <20060509141335.GA4585@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Tue, May 09, 2006 at 11:51:04PM +1000, Russell Shaw wrote:
> 
>>Daniel Jacobowitz wrote:
>>
>>>On Tue, May 09, 2006 at 10:19:49PM +1000, Russell Shaw wrote:
>>>
>>>>Hi,
>>>>When bt shows history inside of a file without debugging
>>>>symbols, how do i find what file it is?
>>>
>>>It looks like your GDB has failed to load libraries.  Try "info
>>>shared".
>>
>>(gdb) info shared
>>No shared libraries loaded at this time.
> 
> Then, your GDB is broken.  Do you get warnings about not being able to
> find the dynamic linker?  How are you starting the program to be
> debugged?  If you're remote debugging, did you use "file"?
> 
> You need to give more details before we can help you.

Hi,
I'm using GNU gdb 6.4-debian on a debian-sid pc.

I debug using: ddd ./myprog

I've been using it for months ok (my program runs on the same pc).

To get rid of these backtrace unknowns, i installed the unstripped
dev and debug packages for various libraries. I assume there's still
some stripped libraries being used. If i can find the name of these
files, i can install debug versions of them.

I assume it's stripped libraries that's causing this?


  reply	other threads:[~2006-05-09 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 12:38 Russell Shaw
2006-05-09 13:51 ` Daniel Jacobowitz
2006-05-09 14:21   ` Russell Shaw
2006-05-09 14:23     ` Daniel Jacobowitz
2006-05-09 14:30       ` Russell Shaw [this message]
2006-05-09 14:34         ` Daniel Jacobowitz
2006-05-09 21:45           ` Russell Shaw

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=4460A544.8060808@netspace.net.au \
    --to=rjshaw@netspace.net.au \
    --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