From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] gdb and external toolchain
Date: Tue, 14 Sep 2010 14:20:07 +0000 (UTC) [thread overview]
Message-ID: <i6o0an$7it$1@dough.gmane.org> (raw)
In-Reply-To: 4C8F7ADB.6070601@carallon.com
On 2010-09-14, William Wagner <will_wagner@carallon.com> wrote:
[...]
> http://sourceware.org/gdb/wiki/FAQ
>
> It says that gdb needs un stripped libpthread and libthread_db
> libraries to work. I'm not sure if this is on the target with
> gdbserver or on the host running gdb.
The latter. I've never had any issues debugging stripped libraries
and binaries on the target.
> Currently buildroot strips the libraries on the target.
That should work fine.
> I've never had a problem debugging with an internal buildroot
> toolchain so presumably buildroot is correct in stripping the
> libraries on the target.
Yes.
> Has anyone seen this before and able to point me in the right
> direction?
The only two things I know about are making sure the libraries are
built with debugging symbols, and then making sure gdb can find them
(by setting the solib-absolute-prefix option in gdb).
--
Grant Edwards grant.b.edwards Yow! I have seen these EGG
at EXTENDERS in my Supermarket
gmail.com ... I have read the
INSTRUCTIONS ...
prev parent reply other threads:[~2010-09-14 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 13:30 [Buildroot] gdb and external toolchain William Wagner
2010-09-13 14:01 ` Thomas Petazzoni
2010-09-13 14:32 ` Grant Edwards
2010-09-13 18:37 ` Anders Darander
2010-09-14 13:38 ` William Wagner
2010-09-14 14:20 ` Grant Edwards [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='i6o0an$7it$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.