Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: gomrioje <gomez.j@ikusi.es>
To: "Jesús Gómez Río" <gomez.j@ikusi.com>
Cc: gdb@sourceware.org
Subject: Re: Debugging pthread in ARM.
Date: Tue, 15 May 2007 17:14:00 -0000	[thread overview]
Message-ID: <1179249238.6692.12.camel@DAFPC5206.ikusi.net> (raw)
In-Reply-To: <20070515125816.GA13421@caradoc.them.org>

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
0x4009b748  0x4009bdf8
No          /app/arm/sc0504/Software/src/libarm9hardpin/debug/src/library/libarm9hardpin.so.0
0x400a5d60  0x400aa2f0
No          /app/arm/bitbaketmp/staging/arm-linux/lib/librt.so.1
0x400c1f70  0x400cbff4
No          /app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0
0x40153278  0x401dc63c
No          /app/arm/bitbaketmp/cross/arm-linux/lib/libstdc++.so.6
0x401ef390  0x40259ae8
No          /app/arm/bitbaketmp/staging/arm-linux/lib/libm.so.6
0x4029a9f8  0x402a0f18
No          /app/arm/bitbaketmp/cross/arm-linux/lib/libgcc_s.so.1
0x402bebb0  0x40393564
No          /app/arm/bitbaketmp/staging/arm-linux/lib/libc.so.6
0x40000740  0x4001491c
No          /app/arm/bitbaketmp/staging/arm-linux/lib/ld-linux.so.2

(for other people reading:
http://sourceware.org/ml/gdb-patches/2007-01/msg00198.html)

Nevertheless, after that I have the same problem.
The response to: info threads is: 1 main....

Something that looks bizarre to me is that gdb converts in the console,
"info threads" to "info thread".
I have checked the threads are running. They have different PIDs, could
be a problem for gdb? 

Regards,





 




On Tue, 2007-05-15 at 08:58 -0400, Daniel Jacobowitz wrote:
> On Tue, May 15, 2007 at 02:49:04PM +0200, gomrioje wrote:
> > - For the gdb (host):
> > set solib-absolute-prefix /dev/null/
> > set
> > solib-search-path /app/arm/debug/:/app/arm/bitbaketmp/staging/arm-linux/lib/
> 
> Don't do that.  Whatever told you to do it was wrong.
> 
> You need to set solib-absolute-prefix to point at something that looks
> like your target's file system, that is, you should be able to add
> /lib/ld-linux.so.2 (or however your platform spells it) and find the
> dynamic linker at that path on the host.
> 
-- 
Jesus Gomez Rio
R&D Technician
Design & Manufacturing Division
gomez.j@ikusi.com
www.ikusi.es
---


  reply	other threads:[~2007-05-15 17:14 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 [this message]
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=1179249238.6692.12.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