Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 17:33:00 -0000	[thread overview]
Message-ID: <1179336833.6692.42.camel@DAFPC5206.ikusi.net> (raw)
In-Reply-To: <20070516153502.GA8429@caradoc.them.org>

Just typing sharedlibrary I get all my libraries with symbols:
From        To          Syms Read   Shared Object Library
0x40024f70  0x4002eff4
Yes         /app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0
0x4007cd60  0x400812f0
Yes         /app/arm/bitbaketmp/staging/arm-linux/lib/librt.so.1
0x400d0278  0x4015963c
Yes         /app/arm/bitbaketmp/cross/arm-linux/lib/libstdc++.so.6
0x4016c390  0x401d6ae8
Yes         /app/arm/bitbaketmp/staging/arm-linux/lib/libm.so.6
0x402179f8  0x4021df18
Yes         /app/arm/bitbaketmp/cross/arm-linux/lib/libgcc_s.so.1
0x4023bbb0  0x40310564
Yes         /app/arm/bitbaketmp/staging/arm-linux/lib/libc.so.6
0x40000740  0x4001491c
Yes         /app/arm/bitbaketmp/staging/arm-linux/lib/ld-linux.so.2


Nevertheless GDB is receiving a SIGNALKILL when I try to set a
breakpoint inside a thread.

You ask me for warnings, there are 2 things:

1. At Host side (gdb console):
(gdb) source prepare_gdb.gdb
0x40000740 in ?? ()

prepare_gdb.gdb is a script:

set $connected=0
shell sleep 1       
target remote 192.168.1.55:1234
set $connected=1
set solib-absolute-prefix /app/arm/bitbaketmp/staging/arm-linux/lib/
set
solib-search-path  /app/arm/bitbaketmp/staging/arm-linux/lib/:/app/arm/sc0504/Software/src/libarm9hardpin/debug/src/library/:/app/arm/bitbaketmp/cross/arm-linux/lib/:/app/arm/sc0504/Software/src/3rdParty/nana-2.5/arm/usr/lib/
continue 

2. At Target side (gdbserver)
gdb: error initializing thread_db library: version mismatch between
libthread_db and libpthread

Regards





> > 
> > Running the aplication in the PC, I get with command backtrace:
> > (gdb) [Thread debugging using libthread_db enabled]
> 
> That's normal.  Only native GDB prints this message.
> 
> > I guess the libraries for the ARM have no symbols charged. Do I need
> > them to debug my application?
> 
> I believe you need symbols for ld.so and libpthread.so.
> 
-- 
Jesus Gomez Rio


  reply	other threads:[~2007-05-16 17:33 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 [this message]
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=1179336833.6692.42.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