Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jason Machacek" <jmachacek@stratos.com>
To: "Paul Pluzhnikov" <ppluzhnikov@google.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 19:04:00 -0000	[thread overview]
Message-ID: <597A11B8CF75534EBE76656E186BF106E0140E@stella.stratos.local> (raw)
In-Reply-To: <8ac60eac0912171052h4b187f79qef9cec04ef2ae791@mail.gmail.com>

>> $ /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.

That was the target's copy of libpthread.so--I did copy it back to the
host before running arm-linux-nm on it as you suggested.


> 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.)

Yes, it was the same target.  Running GDB natively works perfectly with
multiple threads, but when running GDB from my host and connecting to
gdbserver on my target GDB gets confused when the program reaches the
first pthread_create() call.  Unfortunately, my application has recently
become too large to fit in the target's memory while GDB is running, so
I can no longer run GDB natively on my target.

Best regards,
Jason


      reply	other threads:[~2009-12-17 19:04 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
2009-12-17 19:04           ` Jason Machacek [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=597A11B8CF75534EBE76656E186BF106E0140E@stella.stratos.local \
    --to=jmachacek@stratos.com \
    --cc=gdb@sourceware.org \
    --cc=ppluzhnikov@google.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