From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
Ralf Corsepius <ralf.corsepius@rtems.org>
Subject: SPARC GDB Failure
Date: Mon, 07 Sep 2009 14:18:00 -0000 [thread overview]
Message-ID: <4AA5161D.1020102@oarcorp.com> (raw)
Hi,
In anticipation of the upcoming gdb release, Ralf Corsepius has built
RTEMS GDB RPMs based upon gdb-6.8.50.20090902. powerpc/psim
and the mips/jm43904 simulators work fine. But sparc/sis core
dumps in gdb instantly. FWIW "run" works fine also.
I hope someone can help from the backtrace. This is actually our
recommended configuration for new users and testing since it is
so easy to use. When it works of course. :)
I can privately email a sparc executable to debug with if someone
needs it.
Core was generated by `sparc-rtems4.10-gdb ticker.exe'.
Program terminated with signal 11, Segmentation fault.
[New process 3552]
#0 0x080b941b in init_regcache_descr (gdbarch=0x89690a0)
at ../../gdb-6.8.50.20090902/gdb/regcache.c:132
132 descr->sizeof_register[i] = TYPE_LENGTH
(descr->register_type[i]);
(gdb) bt
#0 0x080b941b in init_regcache_descr (gdbarch=0x89690a0)
at ../../gdb-6.8.50.20090902/gdb/regcache.c:132
#1 0x081071be in gdbarch_data (gdbarch=0x89690a0, data=0x88fe3e8)
at ../../gdb-6.8.50.20090902/gdb/gdbarch.c:3526
#2 0x080bac40 in regcache_descr ()
at ../../gdb-6.8.50.20090902/gdb/regcache.c:154
#3 regcache_xmalloc (gdbarch=0x41)
at ../../gdb-6.8.50.20090902/gdb/regcache.c:215
#4 0x080bad65 in get_thread_arch_regcache (ptid=
{pid = 42000, lwp = 0, tid = 42000}, gdbarch=0x89690a0)
at ../../gdb-6.8.50.20090902/gdb/regcache.c:438
#5 0x080bae51 in get_thread_regcache (ptid=
{pid = 42000, lwp = 0, tid = 42000})
at ../../gdb-6.8.50.20090902/gdb/regcache.c:462
#6 0x080bae85 in get_current_regcache ()
at ../../gdb-6.8.50.20090902/gdb/regcache.c:468
#7 0x080eea7e in post_create_inferior (target=0x8820c80, from_tty=0)
at ../../gdb-6.8.50.20090902/gdb/infcmd.c:396
#8 0x080ef408 in run_command_1 (args=0x0, from_tty=1,
tbreak_at_main=<value optimized out>)
at ../../gdb-6.8.50.20090902/gdb/infcmd.c:574
#9 0x08055ac0 in execute_command (p=0x88ee841 "", from_tty=1)
at ../../gdb-6.8.50.20090902/gdb/top.c:453
#10 0x08103e88 in command_handler (command=0x88ee840 "")
at ../../gdb-6.8.50.20090902/gdb/event-top.c:511
#11 0x08104b92 in command_line_handler (rl=0x89ac348 "")
at ../../gdb-6.8.50.20090902/gdb/event-top.c:735
#12 0x009d2507 in rl_callback_read_char () at ../callback.c:205
#13 0x08103fab in rl_callback_read_char_wrapper (client_data=0x0)
at ../../gdb-6.8.50.20090902/gdb/event-top.c:178
#14 0x08103524 in handle_file_event (data={ptr = 0x0, integer = 0})
at ../../gdb-6.8.50.20090902/gdb/event-loop.c:812
#15 0x08102d2b in process_event ()
at ../../gdb-6.8.50.20090902/gdb/event-loop.c:394
#16 0x08103b84 in gdb_do_one_event (data=0x0)
at ../../gdb-6.8.50.20090902/gdb/event-loop.c:459
#17 0x080fe47b in catch_errors (func=0x8103930 <gdb_do_one_event>,
func_args=0x0, errstring=0x8233de9 "", mask=6)
at ../../gdb-6.8.50.20090902/gdb/exceptions.c:510
#18 0x08091e3a in tui_command_loop (data=0x0)
at ../../gdb-6.8.50.20090902/gdb/tui/tui-interp.c:153
#19 0x080feaf4 in current_interp_command_loop ()
at ../../gdb-6.8.50.20090902/gdb/interps.c:291
#20 0x0804dbcb in captured_command_loop (data=0x0)
at ../../gdb-6.8.50.20090902/gdb/main.c:226
#21 0x080fe47b in catch_errors (func=0x804dbc0 <captured_command_loop>,
---Type <return> to continue, or q <return> to quit---q
func_argQuit
(gdb) q
Thanks.
--joel sherrill
RTEMS
next reply other threads:[~2009-09-07 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 14:18 Joel Sherrill [this message]
2009-09-07 16:45 ` Jan Kratochvil
2009-09-07 17:44 ` Doug Evans
2009-09-07 17:54 ` Jan Kratochvil
2009-09-07 18:16 ` Doug Evans
2009-09-07 18:24 ` Joel Brobecker
2009-09-07 18:35 ` Jan Kratochvil
2009-09-07 18:40 ` Joel Sherrill
2009-09-08 6:46 ` Ralf Corsepius
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=4AA5161D.1020102@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
--cc=ralf.corsepius@rtems.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