From: "Dave Bryan" <dave.bryan@gmail.com>
To: insight@sources.redhat.com
Subject: Insight / ARM-Thumb question
Date: Fri, 24 Mar 2006 10:09:00 -0000 [thread overview]
Message-ID: <op.s6ww6qr5010v0s@samsung> (raw)
Hi,
I'm running Insight 6.4 for Arm-elf on Windows XP using Cygwin. The target
is a Philips ARM LPC2214 run via a remote GDB server.
I'm able to download, step & run programs compiled for ARM on the target.
When I compile one or more files for Thumb (mixed ARM & Thumb code) I'm
still able to download & run programs. However, whenever I try to step
into a function compiled for Thumb (from ARM code) I don't actually step
through each line in that function, instead it is as though I've selected
step-over rather than step-into the function.
I've tried two different types of remote GDB server (same target) & both
do the same thing so I don't think there's an issue there. I've set infrun
to 1 in the GDB console window & included the output resulting from
stepping 'into' a Thumb function below:
infrun: proceed (addr=0xffffffff, signal=144, step=1)
infrun: resume (step=1, signal=0)
infrun: wait_for_inferior
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x81004d2c
infrun: stepped into subroutine
infrun: resume (step=0, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x81001c2c
infrun: BPSTATE_WHAT_STEP_RESUME
infrun: stepped to a different line
infrun: stop_stepping
(gdb)
Is being unable to step into a Thumb function a known bug in the Arm-Elf
version of Insight/GDB ?
Thanks
Dave Bryan
next reply other threads:[~2006-03-24 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 10:09 Dave Bryan [this message]
2006-03-24 19:01 ` Keith Seitz
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=op.s6ww6qr5010v0s@samsung \
--to=dave.bryan@gmail.com \
--cc=insight@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).