From: "Harald Schiöberg" <harald@net.t-labs.tu-berlin.de>
To: gdb@sourceware.org
Subject: SIGILL on gdbserver/ARM/uclibc
Date: Mon, 07 Jan 2008 10:31:00 -0000 [thread overview]
Message-ID: <4781FF52.8080905@net.t-labs.tu-berlin.de> (raw)
I know that this issue is on the list every other year, but I found no
working solution for my problem.
I'm currently trying to run gdb/gdbserver on OpenWRT/ARM
(uclibc-0.9.29/gcc-4.1.2, tried gdb 6.3 and 6.7.1,
target is xscale (armv5te), host is ubuntu x86_64,
OpenWRT builds gdb with
gdb_cv_func_sigsetjmp=yes \
$(PKG_BUILD_DIR)/configure \
--prefix=$(TOOLCHAIN_DIR) \
--build=$(GNU_HOST_NAME) \
--host=$(GNU_HOST_NAME) \
--target=$(REAL_GNU_TARGET_NAME) \
$(DISABLE_NLS) \
--without-uiout \
--disable-tui --disable-gdbtk --without-x \
--without-included-gettext \
--enable-threads \
# --disable-gdbmi ## this was commented out for 6.7.1 to compile
I'm getting SIGILL after a breakpoint on the target.
some session-log from 6.7.1:
(gdb) target remote 172.17.2.190:4000
Remote debugging using 172.17.2.190:4000
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
0x400009d0 in ?? ()
(gdb) b main
Note: breakpoint 1 also set at pc 0x8570.
Breakpoint 2 at 0x8570: file hello.c, line 6.
(gdb) c
Continuing.
Program received signal SIGILL, Illegal instruction.
0x00008574 in main () at hello.c:6
6 for (i=0; i< 10; i++)
(gdb) s
Program terminated with signal SIGILL, Illegal instruction.
The program no longer exists.
(gdb) show osabi
The current OS ABI is "auto" (currently "GNU/Linux").
The default OS ABI is "GNU/Linux".
(gdb) set osabi GNU/Linux
(gdb) show osabi
The current OS ABI is "GNU/Linux".
The default OS ABI is "GNU/Linux".
(gdb) target remote 172.17.2.190:4000
Remote debugging using 172.17.2.190:4000
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
0x400009d0 in ?? ()
(gdb) b main
Note: breakpoints 1 and 2 also set at pc 0x8570.
Breakpoint 3 at 0x8570: file hello.c, line 6.
(gdb) c
Continuing.
Program received signal SIGILL, Illegal instruction.
0x00008574 in main () at hello.c:6
6 for (i=0; i< 10; i++)
(gdb) s
breakpoint.c:7845: internal-error: insert_single_step_breakpoint:
Assertion `single_step
_breakpoints[1] == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
--
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
next reply other threads:[~2008-01-07 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 10:31 Harald Schiöberg [this message]
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
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=4781FF52.8080905@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).