From: Eero Tamminen <oak@welho.com>
To: gdb@sources.redhat.com
Subject: GDB 5.2 undefined instruction problem on arm9
Date: Sun, 02 Jun 2002 05:02:00 -0000 [thread overview]
Message-ID: <200206021202.g52C2WA00692@posti.pp.htv.fi> (raw)
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.
I've also tried making a glibc/x86 host version of gdb and arm uClibc-0.9.11
gdbserver. I can connect to the remote gdbserver running on the arm
target with the x86-gdb and x86-gdb recognizes the (statically compiled)
arm-binaries, but when I try to run then through the gdb/gdbserver
combination, I get again SIGILL & "undefined instruction".
Any clues on what might wrong will be greatly appreciated!
Thanks in advance,
- Eero
next reply other threads:[~2002-06-02 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 5:02 Eero Tamminen [this message]
2002-06-02 9:51 ` 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=200206021202.g52C2WA00692@posti.pp.htv.fi \
--to=oak@welho.com \
--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