From: Daniel Jacobowitz <drow@mvista.com>
To: Eero Tamminen <oak@welho.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.2 undefined instruction problem on arm9
Date: Sun, 02 Jun 2002 09:51:00 -0000 [thread overview]
Message-ID: <20020602165111.GA8408@branoic.them.org> (raw)
In-Reply-To: <200206021202.g52C2WA00692@posti.pp.htv.fi>
On Sun, Jun 02, 2002 at 03:15:28PM +0300, Eero Tamminen wrote:
> Hi,
>
> I'm trying to cross-compile gdb 5.2 (released version, not CVS) for arm.
>
> Compilation succeeds and gdb works on the arm (it runs and can display
> it's help, load program etc), but when I try to debug programs with it,
> the debugged program will stop between '_start' and 'main' with SIGILL
> and gdb says "undefined instruction". When I run the program
> _without_ gdb, the program works OK.
>
> This is my first try at trying to compile gdb myself, so I'm wondering
> whether the problem is in how I've configured gdb, my cross-compilation
> environment, gdb arm support, kernel debugging (ptrace?) support
> or what.
>
> Arm version is arm9, I'm configuring gdb with '--target=arm
> --host=arm" and I'm using a cross-compiled glibc with which I link
> gdb statically (using the -static linker flag). Cross-compiler is
> gcc 2.95.3.
The problem is how you configured gdb. Use --target=arm-linux instead;
Linux and hardware monitors signal breakpoints in different ways.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-06-02 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 5:02 Eero Tamminen
2002-06-02 9:51 ` Daniel Jacobowitz [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=20020602165111.GA8408@branoic.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=oak@welho.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