From: "Pelle Svensson" <pelle2004@hotmail.com>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: Remote debugging with gdbserver on ARM
Date: Fri, 16 Feb 2007 12:55:00 -0000 [thread overview]
Message-ID: <BAY120-F1932B5278E43BABD5F8E72B9950@phx.gbl> (raw)
In-Reply-To: <20070215154613.GA22549@caradoc.them.org>
>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/
next prev parent reply other threads:[~2007-02-16 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 15:34 Pelle Svensson
2007-02-15 20:29 ` Daniel Jacobowitz
2007-02-16 12:55 ` Pelle Svensson [this message]
2007-02-16 16:02 ` Daniel Jacobowitz
2007-02-16 16:06 ` Pelle Svensson
2007-02-16 16:50 ` Daniel Jacobowitz
2007-02-17 2:46 ` Pelle Svensson
2007-02-15 0:43 Doug Abbott
2007-02-15 18:26 Pelle Svensson
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=BAY120-F1932B5278E43BABD5F8E72B9950@phx.gbl \
--to=pelle2004@hotmail.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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