Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jon Grant <jg@jguk.org>
To: gdb@sourceware.org
Subject: Re: Two gdb 6.4 usage queries
Date: Sat, 11 Nov 2006 22:06:00 -0000	[thread overview]
Message-ID: <455649D4.6050706@jguk.org> (raw)
In-Reply-To: <454578F3.9030703@jguk.org>

Hello,

Don't think I missed any reply.. I wonder if anyone could help me with
some info on how solve the problems?

Please include my email address in any reply.
Kind regards
Jon

Jon Grant elucidated on 30/10/06 04:00:
> Hello,
> 
> I have to queries, I hope someone will be able explain or point me to
> documentation.
> (I am running Kubuntu 6.06 on a 32bit Althon.)
> 
> 1) Shared library methods are relocated when they are used by a program,
> is there a way to view the present running address of these shared
> library functions/methods from gdb?
> 
> 2) I would like to get to see the same backtrace that the kde crash
> handler has generated
> 
> callstack like:
> [KCrash handler]
> #6  0x00000000 in ?? ()
> #7  0xb7182f3e in QApplication::internalNotify () from
> /usr/lib/libqt-mt.so.3
> #8  0xb718313a in QApplication::notify () from /usr/lib/libqt-mt.so.3
> #9  0xb78617ab in KApplication::notify () from /usr/lib/libkdecore.so.4
> #10 0xb71141c5 in QApplication::sendSpontaneousEvent ()
>    from /usr/lib/libqt-mt.so.3
> <snip>
> 
> When I attach the to crashed process with gdb all I can get is this:
> 
> $ gdb /usr/bin/ark 6582
> GNU gdb 6.4-debian
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> 
> Attaching to program: /usr/bin/ark, process 6582
> (no debugging symbols found)
> 0xffffe410 in __kernel_vsyscall ()
> (gdb) bt
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb7d09110 in ?? ()
> #2  0xb7d08f3c in ?? ()
> #3  0xbfc11bb4 in ?? ()
> #4  0xbfc11bb4 in ?? ()
> #5  0x00000000 in ?? ()
> 
> Thanks for any help.
> 
> Please include my email address in any reply.
> 
> Kind regards
> Jon
> 


  reply	other threads:[~2006-11-11 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30  3:59 Jon Grant
2006-11-11 22:06 ` Jon Grant [this message]
2006-11-11 22:28   ` Mark Kettenis
2006-11-12  1:25     ` Jon Grant

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=455649D4.6050706@jguk.org \
    --to=jg@jguk.org \
    --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