Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Markus.Grunwald@pruftechnik.com
Cc: gdb@sourceware.org
Subject: Re: gdb 6.6: incomplete backtraces ?
Date: Thu, 08 Mar 2007 16:06:00 -0000	[thread overview]
Message-ID: <20070308160646.GB8042@caradoc.them.org> (raw)
In-Reply-To: <OFA2E529A2.BABC5212-ONC1257298.00547007-C1257298.0056CA29@pruftechnik.com>

On Thu, Mar 08, 2007 at 04:47:37PM +0100, Markus.Grunwald@pruftechnik.com wrote:
> Catchpoint 1 (forked process 27093), 0xb7f10410 in ?? ()
> (gdb) bt
> #0  0xb7f10410 in ?? ()
> #1  0x00000001 in ?? ()
> #2  0x00000000 in ?? ()
> (gdb) info shared
> From        To          Syms Read   Shared Object Library
> 0xb7f11790  0xb7f222cf  Yes         /lib/ld-linux.so.2
> 0xb7eeb0e0  0xb7ef7a74  Yes         /lib/libbz2.so.1.0
> 0xb7700f40  0xb7bf0880  Yes         /opt/qt/x86/qt3/lib/libqt-mt.so.3
> [...]
> 
> Hmm, seems we didn't hit anything... 

Check /proc/27093/maps.  Most likely it's the .plt section of
ld-linux.so.2.
> Sounds interresing... But I am currently testing a lot of gdb stuff here 
> and don't want to interfere with my colleagues who work on the same 
> machine, so I don't want to use --prefix=/usr ...

You don't need to install it there, just configure it there.  Or set
debug-file-directory by hand - see the manual for more on that.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-03-08 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 15:04 Markus.Grunwald
2007-03-08 15:15 ` Daniel Jacobowitz
2007-03-08 15:47   ` Markus.Grunwald
2007-03-08 16:06     ` Daniel Jacobowitz [this message]

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=20070308160646.GB8042@caradoc.them.org \
    --to=drow@false.org \
    --cc=Markus.Grunwald@pruftechnik.com \
    --cc=gdb@sourceware.org \
    /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