From: Andrew STUBBS <andrew.stubbs@st.com>
To: GDB List <gdb@sourceware.org>
Subject: Re: Breakpoints in delay slots
Date: Fri, 20 Oct 2006 08:51:00 -0000 [thread overview]
Message-ID: <45388E13.6000408@st.com> (raw)
In-Reply-To: <453608FC.2040201@st.com>
In reply to the message from Daniel that I never got, but appears in the
web archive. (Now that I look I never got my own message back either.)
> This is a remarkable mess. Unsurprisingly you aren't the first person
> to have this sort of problem, so GDB has a certain amount of support
> for delay slots, but MIPS at least is much friendlier: you can use the
> same breakpoint instruction, and there's a bit in the cause register
> that lets you know you were in a delay slot.
>
> When you have a symbol file, does that suffice to let you know what
> is code and what is data?
Unfortunately not. At least, the only way I can think of is to check
whether it has a line number or not, and the answer is that even the
data has a line number - that of the instruction immediately preceding it.
Andrew
next prev parent reply other threads:[~2006-10-20 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 10:59 Andrew STUBBS
2006-10-18 14:04 ` Daniel Jacobowitz
2006-10-18 18:51 ` Michael Snyder
2006-10-19 9:52 ` Andrew STUBBS
2006-10-19 23:20 ` Michael Snyder
2006-10-19 19:51 ` Mark Kettenis
2006-10-20 8:42 ` Andrew STUBBS
2006-10-22 19:47 ` Mark Kettenis
2006-10-20 8:51 ` Andrew STUBBS [this message]
2006-10-20 14:26 ` Daniel Jacobowitz
2006-10-20 21:18 ` Jim Blandy
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=45388E13.6000408@st.com \
--to=andrew.stubbs@st.com \
--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