Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] gdb and external toolchain
Date: Tue, 14 Sep 2010 14:38:35 +0100	[thread overview]
Message-ID: <4C8F7ADB.6070601@carallon.com> (raw)
In-Reply-To: <AANLkTimDzh0kHMk2fjBqMzW8r5r3EAk==q+A7QsH6S9L@mail.gmail.com>

  Thanks for the help. I basically did the same to copy over gdbserver.

I now have a problem where gdb is unable to debug thread creation, it 
hangs when stepping over pthread_create. Searching on the web I have 
found various comments that refer you to  point 6 in the FAQ at 
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. Currently buildroot strips the libraries on the target.

I've never had a problem debugging with an internal buildroot toolchain 
so presumably buildroot is correct in stripping the libraries on the 
target. Has anyone seen this before and able to point me in the right 
direction?

Thanks
Will

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2010-09-14 13:38 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 [this message]
2010-09-14 14:20     ` Grant Edwards

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=4C8F7ADB.6070601@carallon.com \
    --to=will_wagner@carallon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox