From: gomrioje <gomez.j@ikusi.es>
To: gdb@sourceware.org
Subject: Debugging pthread in ARM.
Date: Tue, 15 May 2007 12:49:00 -0000 [thread overview]
Message-ID: <1179233344.1389.18.camel@DAFPC5206.ikusi.net> (raw)
I am not able to see the point of Daniel (mea culpa).
I have readen documentation as recommended by Daniel and William.
Maybe trying again...
The application uses: pthread_create.
For that I am using as library (-lpthread):
libpthread.so.0->libpthread-0.10.so
For debugging purposes, I am using gdbserver in the target (AT91RM9200).
gdbserver must use library: libthread_db.so.1->libthread_db-1.0.so
Now I describe the problem:
1. When I set a breakpoint inside a thread code, I get a SIGTRAP.
2. After creating several threads (POSIX: pthread_create),
command: info threads, result in: 1 main...............
3. Sometimes after running a while, I get a message in the gdbserver
console:
Gdb: error initalizing thread_db library: version mismatch between
libthread_db and libpthread
Both of the libraries come from the same Debian distribution, for ARM
architecture.
Daniel mentions problem pointing to libraries. For such situation,
the config is:
- For the gdbserver:
export LD_LIBRARY_PATH=/lib:/usr/lib/:/app/arm/debug/:$LD_LIBRARY_PATH
- For the gdb (host):
set solib-absolute-prefix /dev/null/
set
solib-search-path /app/arm/debug/:/app/arm/bitbaketmp/staging/arm-linux/lib/
I could miss something. Some ideas ?
Regards,
> Thanks for the link.
> But I guess my problem is not described there.
> I have another message:
> Gdb: error initalizing thread_db library: version mismatch between libthread_db and libpthread
>
> I have read in the mailing list that both should have the same glibc.
> (what do you mean there?).
>
> In another hand, I am already pointing solib-absolute-prefix to the directory libraries.
If you're doing that, and getting the above error, then you are not
pointing to the correct libraries.
--
Jesus Gomez Rio
R&D Technician
Design & Manufacturing Division
gomez.j@ikusi.com
www.ikusi.es
---
next reply other threads:[~2007-05-15 12:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 12:49 gomrioje [this message]
2007-05-15 12:58 ` Daniel Jacobowitz
2007-05-15 17:14 ` gomrioje
2007-05-15 17:21 ` Daniel Jacobowitz
2007-05-16 15:27 ` gomrioje
2007-05-16 15:35 ` Daniel Jacobowitz
2007-05-16 17:33 ` gomrioje
2007-05-16 17:38 ` Daniel Jacobowitz
2007-05-16 17:46 ` gomrioje
2007-05-16 17:52 ` Daniel Jacobowitz
2007-05-16 18:05 ` gomrioje
2007-05-16 18:11 ` Daniel Jacobowitz
2007-05-17 8:11 ` gomrioje
2007-05-17 9:28 ` Baurzhan Ismagulov
2007-05-17 12:34 ` gomrioje
2007-05-17 12:42 ` Daniel Jacobowitz
2007-05-15 18:42 ` Williams, Allen
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=1179233344.1389.18.camel@DAFPC5206.ikusi.net \
--to=gomez.j@ikusi.es \
--cc=gdb@sourceware.org \
/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