From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Jason Machacek <jmachacek@stratos.com>
Cc: gdb@sourceware.org
Subject: Re: Cross-platform, multithreaded debugging (x86 to ARM) with gdb and gdbserver not recognizing threads
Date: Thu, 17 Dec 2009 18:53:00 -0000 [thread overview]
Message-ID: <8ac60eac0912171052h4b187f79qef9cec04ef2ae791@mail.gmail.com> (raw)
In-Reply-To: <597A11B8CF75534EBE76656E186BF106E01401@stella.stratos.local>
On Thu, Dec 17, 2009 at 10:38 AM, Jason Machacek <jmachacek@stratos.com> wrote:
> Sorry about that, I misread your last message. libpthread.so isn't
> stripped:
>
> $ /opt/crosstool/gcc-3.4.4-glibc-2.3.2/arm-linux/bin/arm-linux-nm
> libpthread-0.10.so | egrep 'version|threads_events'
> 0000de40 r __linuxthreads_version
> 00018e68 b __pthread_threads_events
AFAIU, this is the host copy of libpthread.
One common mistake is stripping it *on target*. Hence I asked to copy it
back and run nm on what is actually on target.
Of course you could just 'ls -l' or md5sum to verify that host and target
copies are identical.
> Yes, I did mean that I statically linked my application with libc.a.
> Perhaps I'll reexamine my build environment as this may be the root of
> my problems with GDB. When running GDB natively on my target, I had no
> problems debugging my application despite it being statically linked.
Was it on the same target you are using now? (That would rule out stripped
libpthread, or libpthread/libthread_db mismatch, as gdb and gdbserver
should be similarly broken.)
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-12-17 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 23:01 Jason Machacek
2009-12-17 4:44 ` Paul Pluzhnikov
2009-12-17 18:01 ` Jason Machacek
2009-12-17 18:21 ` Paul Pluzhnikov
2009-12-17 18:38 ` Jason Machacek
2009-12-17 18:53 ` Paul Pluzhnikov [this message]
2009-12-17 19:04 ` Jason Machacek
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=8ac60eac0912171052h4b187f79qef9cec04ef2ae791@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=jmachacek@stratos.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