This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Remote debugging with gdbserver on ARM
- From: "Pelle Svensson" <pelle2004 at hotmail dot com>
- To: drow at false dot org
- Cc: gdb at sourceware dot org
- Date: Fri, 16 Feb 2007 13:43:42 +0100
- Subject: Re: Remote debugging with gdbserver on ARM
- Bcc:
From: Daniel Jacobowitz <drow@false.org>
To: Pelle Svensson <pelle2004@hotmail.com>
CC: gdb@sourceware.org
Subject: Re: Remote debugging with gdbserver on ARM
Date: Thu, 15 Feb 2007 10:46:13 -0500
On Wed, Feb 14, 2007 at 04:14:04PM +0100, Pelle Svensson wrote:
> shared library path: (i386host)//home/dev/nfs/targetfs/lib, (target path
is
> /lib)
> issued set solib-absolute-prefix /dev/null
Making your front end not do these, but instead set the prefix...
Things work much better with release 6.6 and not setting
solib-absolute-prefix.
There is still a 'Cannot access memory at address 0x0' before reaching
main().
Stepping works find in main().
Program runs much longer now, but stops at SIG32.
Console stuff:
=========
Cannot access memory at address 0x0
Cannot access memory at address 0x0
info program
Debugging a target over a serial line.
Program stopped at 0x40077228.
It stopped with signal SIG32, Real-time event 32.
Type "info stack" or "info registers" for more information.
info stack
#0 0x40077228 in ?? () from /lib/libpthread.so.0
After issued 'signal SIG32' for continuing things seems to be not right, can
it be the
access at adress 0x0 or that the libpthread dosen't have any debug-info?
_________________________________________________________________
Senaste nytt om Paris och Lindsey http://starlounge.msn.se/