From: gomrioje <gomez.j@ikusi.es>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Jesús Gómez Río" <gomez.j@ikusi.com>, gdb@sourceware.org
Subject: Re: Debugging pthread in ARM.
Date: Wed, 16 May 2007 18:05:00 -0000 [thread overview]
Message-ID: <1179338692.6692.56.camel@DAFPC5206.ikusi.net> (raw)
In-Reply-To: <20070516175207.GA15384@caradoc.them.org>
Ok, then:
Target side:
# /lib/libc.so.6
GNU C Library development release version 2.3.90, by Roland McGrath et
al.
Compiled by GNU CC version 3.4.4 (release) (CodeSourcery ARM Q1cvs
2005).
Compiled on a Linux 2.6.11 system on 2005-11-25.
Host size:
$ strings /app/arm/bitbaketmp/staging/arm-linux/lib/libpthread-0.10.so
...
libc.so.6
ld-linux.so.2
libpthread.so.0
GLIBC_2.0
GLIBC_2.1
GLIBC_2.1.1
GLIBC_2.1.2
GLIBC_2.2
GLIBC_2.2.3
GLIBC_2.2.6
GLIBC_2.3.2
GLIBC_PRIVATE
GLIBC_2.1.3
GLIBC_2.3
/proc/self/maps
%x-%x
2.3.90
/proc/sys/kernel/version
__fcntl_nocancel
do_pread
do_pwrite
/lib/ld-linux.so.2
Regards,
> > I have tried, and I get the same result.
> >
> > Could it be link to:
> > http://sources.redhat.com/ml/gdb/2003-06/msg00535.html ?
>
> No, that has nothing to do with it.
>
> Try looking at the libpthread.so GDB opens on your host with
> "strings". Search for its version number in the output. Then
> check the version number on your target by running /lib/libc.so.6 as a
> program and looking at its output.
>
next prev parent reply other threads:[~2007-05-16 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 12:49 gomrioje
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 [this message]
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=1179338692.6692.56.camel@DAFPC5206.ikusi.net \
--to=gomez.j@ikusi.es \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=gomez.j@ikusi.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