From: Daniel Jacobowitz <drow@mvista.com>
To: Erik Andersen <andersen@codepoet.org>
Cc: Dmytro Bablinyuk <dmytro.bablinyuk@tait.co.nz>, gdb@sources.redhat.com
Subject: Re: How to configure gdb on arm-linux (for CDB89712)
Date: Sat, 08 Feb 2003 15:55:00 -0000 [thread overview]
Message-ID: <20030208155502.GA27662@nevyn.them.org> (raw)
In-Reply-To: <20030208103636.GA11381@codepoet.org>
On Sat, Feb 08, 2003 at 03:36:36AM -0700, Erik Andersen wrote:
> On Fri, 7 Feb 2003 08:27:41 -0500, Daniel Jacobowitz wrote:
> > This is a known problem between GDB 5.3 and uclibc: uclibc
> > doesn't leave the identifying marks that GDB uses to figure out
> > that something is a "Linux" binary rather than a "generic ELF"
> > binary. Try a CVS snapshot of GDB and I bet it'll work.
>
> I've just added the .note.ABI-tag section to uClibc's crt0.o
> and crt1.o for arm, which lets gdb 5.3 now behave itself when
> debugging uClibc binaries on arm. I just tried it, and it
> worked as expected -- no more SIGILLs...
Note that the next release will behave OK even without it, I tink.
> Daniel -- is arm the only architecture for which the
> .note.ABI-tag section is required for proper gdb behavior?
I don't know offhand; really, it affects all of them, but ARM is just
the most visible failure.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-08 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 10:38 Dmytro Bablinyuk
2003-02-07 13:27 ` Daniel Jacobowitz
2003-02-08 10:36 ` Erik Andersen
2003-02-08 15:55 ` Daniel Jacobowitz [this message]
2003-02-07 22:35 Dmytro Bablinyuk
2003-02-08 1:38 ` Dmytro Bablinyuk
2003-02-10 20:31 ` Daniel Jacobowitz
2003-02-10 23:50 ` Dmytro Bablinyuk
2003-02-10 23:53 ` Daniel Jacobowitz
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=20030208155502.GA27662@nevyn.them.org \
--to=drow@mvista.com \
--cc=andersen@codepoet.org \
--cc=dmytro.bablinyuk@tait.co.nz \
--cc=gdb@sources.redhat.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