From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB List <gdb@sourceware.org>
Subject: Re: Breakpoints in delay slots
Date: Thu, 19 Oct 2006 23:20:00 -0000 [thread overview]
Message-ID: <1161300019.9942.74.camel@localhost.localdomain> (raw)
In-Reply-To: <45374ADE.3040401@st.com>
On Thu, 2006-10-19 at 10:52 +0100, Andrew STUBBS wrote:
> Michael Snyder wrote:
> > Sorry to be terse, but...
> >
> > (1) -O0
>
> Actually it can still happen that the first instruction in a line is the
> nop in the delay slot, but that can be considered a compiler bug.
>
> > (2) "Don't do that".
>
> That's hardly the developer's choice.
>
> In the real world people sometimes have to debug optimised code and
> "don't do it" is not a useful answer.
Well, I know, but in some cases it's the only answer we have.
There are some problems in debugging optimized code that are
not soluble, or not practically soluble.
Moreover, I separated (1) from (2) deliberately. In the absence
of the compiler placing a delay slot at the beginning of a function
or line, for the user to explicitly place a breakpoint in a delay
slot can arguably be called pilot error.
next prev parent reply other threads:[~2006-10-19 23:20 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 [this message]
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
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=1161300019.9942.74.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=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