List Info

Thread: Re: Debugging pthread in ARM.




Re: Debugging pthread in ARM.
country flaguser name
United States
2007-05-16 13:10:55
I'm out of ideas.  I recommend you debug gdbserver to see
why it
thinks there is a mismatch.

-- 
Daniel Jacobowitz
CodeSourcery

Re: Debugging pthread in ARM.
user name
2007-05-17 03:11:41
Not able to debug gdbserver.
Maybe that is the problem...
I get the gdbserver from Debian distribution for ARM
architecture.
file gdbserver
gdbserver: ELF 32-bit LSB executable, ARM, version 1 (ARM),
for
GNU/Linux 2.4.1, dynamically linked (uses shared libs), for
GNU/Linux
2.4.1, stripped

It makes sense to you?

On Wed, 2007-05-16 at 14:10 -0400, Daniel Jacobowitz wrote:
> I'm out of ideas.  I recommend you debug gdbserver to
see why it
> thinks there is a mismatch.
> 


Re: Debugging pthread in ARM.
user name
2007-05-17 07:34:12
Thanks all, specially Daniel.
Changing the library libpthread to the right version, 
let me to set breakpoints in the threads.

But still something is not working:
In a simple application, I get an infinite backtrace in the
gdb console,
when it stops in a breakpoint inside a thread.
(always as:
#149 0x400c3f78 in pthread_start_thread ()
from
/app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0
#150 0x400c3f78 in pthread_start_thread ()
from
/app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0
#151 0x400c3f78 in pthread_start_thread ()
from
/app/arm/bitbaketmp/staging/arm-linux/lib/libpthread.so.0
..........)




On Wed, 2007-05-16 at 14:10 -0400, Daniel Jacobowitz wrote:
> I'm out of ideas.  I recommend you debug gdbserver to
see why it
> thinks there is a mismatch.
> 


[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )