From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>,
Andrew Cagney <ac131313@ges.redhat.com>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] enable software single step on alpha-osf
Date: Fri, 16 Aug 2002 12:40:00 -0000 [thread overview]
Message-ID: <1020816194018.ZM31084@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: [RFA] enable software single step on alpha-osf" (Aug 16, 3:26pm)
On Aug 16, 3:26pm, Daniel Jacobowitz wrote:
> > Expressions like:
> >
> > /* Pass TRUE if our reason for stopping is something other
> > than hitting a breakpoint. We do this by checking that
> > 1) stepping is going on and 2) we didn't hit a breakpoint
> > in a signal handler without an intervening stop in
> > sigtramp, which is detected by a new stack pointer value
> > below any usual function calling stack adjustments. */
> > (currently_stepping (ecs)
> > && prev_pc != stop_pc - DECR_PC_AFTER_BREAK
> > && !(step_range_end && INNER_THAN (read_sp (),(step_sp - 16)))));
>
> Which reminds me - does that use of INNER_THAN make even the slightest
> sense on stack-grows-up architectures? I don't think it does.
I don't think so either.
Also, that magical value of 16 just can't be right for all architectures.
But this is one of those areas where we have to be *very* careful.
We can attempt to make well-meaning changes and then discover many
months later that we've broken something that used work.
For the above, I think we need to figure out the intent behind the
condition
INNER_THAN (read_sp (),(step_sp - 16),
and then write an architecture dependent method for it.
Kevin
next prev parent reply other threads:[~2002-08-16 19:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 13:55 Joel Brobecker
2002-07-22 4:19 ` Eli Zaretskii
2002-07-25 16:38 ` Andrew Cagney
2002-07-26 10:17 ` Jason R Thorpe
2002-07-31 10:28 ` Joel Brobecker
2002-08-04 16:42 ` Andrew Cagney
2002-08-05 11:49 ` Joel Brobecker
2002-08-05 20:01 ` Andrew Cagney
2002-08-16 10:11 ` Andrew Cagney
2002-08-16 11:21 ` Joel Brobecker
2002-08-16 12:11 ` Andrew Cagney
2002-08-16 12:26 ` Daniel Jacobowitz
2002-08-16 12:40 ` Kevin Buettner [this message]
2002-08-16 14:40 ` Peter.Schauer
2002-08-16 12:41 ` Andrew Cagney
2002-08-16 16:05 ` Joel Brobecker
2002-08-16 16:45 ` Andrew Cagney
2002-08-16 17:58 ` Joel Brobecker
2002-08-16 18:23 ` Andrew Cagney
2002-08-16 23:29 ` Joel Brobecker
2002-08-20 8:55 ` Joel Brobecker
2002-08-20 17:29 ` Andrew Cagney
2002-08-20 19:14 ` Daniel Jacobowitz
2002-08-21 7:01 ` Joel Brobecker
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=1020816194018.ZM31084@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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