public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: arm-elf-gdb crash
Date: Fri, 06 May 2005 03:27:00 -0000	[thread overview]
Message-ID: <7f45d9390505052026171614fd@mail.gmail.com> (raw)

arm-elf-gdb 6.2.1 crashed after issuing a 'step' command. Here's the
commands leading up to it and the backtrace.

Cheers,
Shaun

$ arm-elf-gdb --version
GNU gdb 6.2.1
...
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
$ arm-elf-gdb hello
(gdb) target remote bdi:2001
0x02020974 in ?? ()
(gdb) lo
Loading section .text, size 0x1edc lma 0x2080000
Loading section .init, size 0x14 lma 0x2081edc
Loading section .fini, size 0x10 lma 0x2081ef0
Loading section .rodata, size 0x1e lma 0x2081f00
Loading section .eh_frame, size 0x4 lma 0x2081f20
Loading section .ctors, size 0x8 lma 0x2082024
Loading section .dtors, size 0x8 lma 0x208202c
Loading section .jcr, size 0x4 lma 0x2082034
Loading section .data, size 0x81c lma 0x2082038
Start address 0x2080000, load size 10066
Transfer rate: 80528 bits/sec, 251 bytes/write.
(gdb) b main
Breakpoint 1 at 0x208014c: file hello.c, line 8.
(gdb) c
Continuing.

Breakpoint 1, main () at hello.c:8
8       }
(gdb) s
Segmentation fault (core dumped)

$ gdb arm-elf-gdb core
(gdb) bt
#0  0x0808ba69 in get_frame_pc (frame=0x0) at ../../gdb/frame.c:1886
#1  0x080f9e8d in insert_step_resume_breakpoint (return_frame=0x0,
    ecs=0xbfffee50) at ../../gdb/infrun.c:2684
#2  0x080f8f3d in handle_inferior_event (ecs=0xbfffee50)
    at ../../gdb/infrun.c:1984
#3  0x080f85dc in wait_for_inferior () at ../../gdb/infrun.c:998
#4  0x080f83f5 in proceed (addr=1, siggnal=TARGET_SIGNAL_DEFAULT, step=1)
    at ../../gdb/infrun.c:821
#5  0x080f56b5 in step_1 (skip_subroutines=0, single_inst=0, count_string=0x0)
    at ../../gdb/infcmd.c:688
#6  0x080f54df in step_command (count_string=0x0, from_tty=1)
    at ../../gdb/infcmd.c:577
#7  0x080a9419 in do_cfunc (c=0x0, args=0x0, from_tty=0)
    at ../../gdb/cli/cli-decode.c:57
#8  0x080ab37c in cmd_func (cmd=0x82c4768, args=0x0, from_tty=0)
    at ../../gdb/cli/cli-decode.c:1561
#9  0x080836cd in execute_command (p=0x82af071 "", from_tty=1)
    at ../../gdb/top.c:744
#10 0x081056ff in command_handler (command=0x82af070 "s")
    at ../../gdb/event-top.c:500
#11 0x08105b45 in command_line_handler (rl=0x832a040 "")

             reply	other threads:[~2005-05-06  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  3:27 Shaun Jackman [this message]
2005-05-06  3:31 ` Daniel Jacobowitz
2005-05-06  3:49   ` Shaun Jackman
2005-05-06  4:08     ` Daniel Jacobowitz
2005-05-06 15:40       ` Shaun Jackman
2005-05-06 15:42         ` Daniel Jacobowitz
2005-05-06 16:03           ` Shaun Jackman
2005-09-20 16:35             ` Shaun Jackman

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=7f45d9390505052026171614fd@mail.gmail.com \
    --to=sjackman@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).