From: gomrioje <gomez.j@ikusi.es>
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 15:27:00 -0000 [thread overview]
Message-ID: <1179329274.6692.30.camel@DAFPC5206.ikusi.net> (raw)
In-Reply-To: <20070515172110.GA27784@caradoc.them.org>
Running the aplication in the PC, I get with command backtrace:
(gdb) [Thread debugging using libthread_db enabled]
I don't get this message in the cross-debugging with arm.
Both the gdb and the gdbserver are:
GNU gdbserver 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
gdbserver is free software, covered by the GNU General Public License.
This gdbserver was configured as "arm-linux-gnu"
GNU gdb 6.4.90
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "--host=i686-linux --target=arm-linux".
I guess the libraries for the ARM have no symbols charged. Do I need
them to debug my application?
Regards,
On Tue, 2007-05-15 at 13:21 -0400, Daniel Jacobowitz wrote:
> On Tue, May 15, 2007 at 07:13:58PM +0200, gomrioje wrote:
> > Thanks Daniel, I point solib-absolute, right now my libraries (info
> > sharedlibrary) are like that:
> >
> >
> > >From To Syms Read Shared Object Library
> > 0x400284d8 0x400859a4
> > No /app/arm/bitbaketmp/staging/arm-linux/lib/libsqlite.so.0
>
> Something is still wrong, since if GDB had found the libraries it
> would have read in symbols automatically. Are you getting any
> warnings? Are you sure they are exactly the same versions?
>
> ld-linux.so.2 should be under your solib-absolute-prefix.
>
>
--
Jesus Gomez Rio
R&D Technician
Design & Manufacturing Division
gomez.j@ikusi.com
www.ikusi.es
---
next prev parent reply other threads:[~2007-05-16 15:27 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 [this message]
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=1179329274.6692.30.camel@DAFPC5206.ikusi.net \
--to=gomez.j@ikusi.es \
--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