From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Leon Pollak <leonp@plris.com>
Cc: gdb@sourceware.org
Subject: Re: Restarting gdbserver
Date: Sun, 23 Jan 2011 18:20:00 -0000 [thread overview]
Message-ID: <20110123181935.GA25767@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201101232005.43430.leonp@plris.com>
On Sun, 23 Jan 2011 19:05:42 +0100, Leon Pollak wrote:
> OK, to check myself and understand your explanation, I compiled the same
> application in the "normal" Fedora 12 - it does show the backtrace.
OK, so you do not have debug info in either case.
But on x86* Fedora you can backtrace any system code even if you do not have
the debug info installed. (This is not true for any x86* code but Fedora is
using -fasynchronous-unwind-tables so it can backtrace even
-fomit-frame-pointer code without debug info.)
On arm I guess - I do not know arm - you need debug info for the backtrace.
But this is very montavista distro specific question and in fact offtopic here.
> From To Syms Read Shared Object Library
[...]
> 0x008145e0 0x00820518 Yes (*) /lib/libpthread.so.0
[...]
> (*): Shared library is missing debugging information.
> (gdb) bt
> #0 0x00110430 in __kernel_vsyscall ()
> #1 0x0081a22c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
This record shows the debug info is missing. You can try
`debuginfo-install glibc' on Fedora to get the debug info. Still it does not
affect the capability of backtracing on x86*.
> And I searched my Fedora installatoin - no *debug*.so at all.
You would need to install it first:
# repoquery -q --enablerepo='fedora*-debuginfo' glibc-debuginfo
glibc-debuginfo-0:2.12.90-17.i686
# debuginfo-install glibc
# ls -lL /usr/lib/debug/lib/libpthread.so.0.debug
-r--r--r-- 1 root root 708656 Dec 14 17:53 /usr/lib/debug/lib/libpthread.so.0.debug
(Adjusted from x86_64 as you seem to run 32bit.)
Regards,
Jan
next prev parent reply other threads:[~2011-01-23 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 9:25 Leon Pollak
2011-01-20 9:36 ` Jan Kratochvil
2011-01-20 14:07 ` Leon Pollak
2011-01-20 14:11 ` Jan Kratochvil
2011-01-20 14:55 ` Leon Pollak
2011-01-20 17:29 ` Jan Kratochvil
2011-01-21 22:48 ` Leon Pollak
2011-01-23 13:28 ` Jan Kratochvil
2011-01-23 16:39 ` Leon Pollak
2011-01-23 16:48 ` Jan Kratochvil
2011-01-23 18:01 ` Leon Pollak
2011-01-23 18:20 ` Jan Kratochvil [this message]
2011-01-23 18:25 ` Andreas Schwab
2011-01-20 14:10 Leon Pollak
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=20110123181935.GA25767@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=leonp@plris.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