From: "Harald Schiöberg" <harald@net.t-labs.tu-berlin.de>
To: "Harald Schiöberg" <harald@net.t-labs.tu-berlin.de>, gdb@sourceware.org
Subject: Re: SIGILL on gdbserver/ARM/uclibc
Date: Mon, 07 Jan 2008 17:32:00 -0000 [thread overview]
Message-ID: <47826212.8060207@net.t-labs.tu-berlin.de> (raw)
In-Reply-To: <20080107151939.GA6032@caradoc.them.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Jacobowitz wrote:
> On Mon, Jan 07, 2008 at 02:49:21PM +0100, Harald Schiöberg wrote:
>> uhm, where do I find some info about reading the debug output.
>
> In the manual. But I can pick out the instruction for you, here...
>
>> Sending packet: $X844c,4:�237\000\001#84...Ack
>
> Of course your mailer seems to have garbled that a little so I can't
> tell exactly what character it was. But it's something 0237 000 001.
> That's arm_linux_arm_be_breakpoint. If you're using
> arm-linux-gnueabi, it's wrong; if you're using old-ABI it should be
> correct.
>
thank you, for everyone searching the archive:
"set arm abi AAPCS" (instead of default APCS)
fixed it.
>> warning: no loadable sections found in added symbol-file
>> /data/harald/root/lib/ld-uClibc
>> .so.0
>
> Is that really the right file? It looks corrupt.
not yet sure what it is, but:
root@OpenWrt:/nfs/tmp# ldd ./hello
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4000e000)
libc.so.0 => /lib/libc.so.0 (0x40020000)
libc.so.0 => /lib/libc.so.0 (0x40083000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40000000)
he furthermore now claims:
warning: no loadable sections found in added symbol-file
/data/harald/root/lib/libgcc_s.so.1
warning: no loadable sections found in added symbol-file
/data/harald/root/lib/libc.so.0
I have to dig a little bit deeper, most likely OpenWRT is guilty here,
unless gdb does something really weird.
Thanks a lot
Harald
- --
Harald Schiöberg
Technische Universität Berlin | T-Laboratories | FG INET
www: http://www.net.t-labs.tu-berlin.de
Phone: +49-(0)30-8353-58476 | Fax: +49-(0)391 534 783 47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHgmISJgyxs71kcx4RAsCmAKDSCXCrjgqgB6yqoGq298C/RKXbHwCg0X4m
CyRJBawVugTYLck1dLmECwo=
=aEIf
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-01-07 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 10:31 Harald Schiöberg
2008-01-07 13:15 ` Daniel Jacobowitz
2008-01-07 13:49 ` Harald Schiöberg
2008-01-07 15:20 ` Daniel Jacobowitz
2008-01-07 17:32 ` Harald Schiöberg [this message]
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=47826212.8060207@net.t-labs.tu-berlin.de \
--to=harald@net.t-labs.tu-berlin.de \
--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