From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: Unable to step over (n and ni) on mipsel-linux...
Date: Mon, 23 Aug 2004 19:22:00 -0000 [thread overview]
Message-ID: <20040823192159.GA12007@nevyn.them.org> (raw)
In-Reply-To: <412A3E3F.3020409@avtrex.com>
On Mon, Aug 23, 2004 at 11:58:07AM -0700, David Daney wrote:
> For next and nexti it does not need to analyse the stack frames.
>
> I have half a mind to hack up mips-tdep.c:mips32_next_pc so that it
> returns the address following the jal/jalr if step_over_calls ==
> STEP_OVER_ALL or some such thing.
IMO, this is reasonable on targets where we're using software single
step anyway. It's also reasonable if trust_readonly_sections is true.
Would anyone object to an optional gdbarch method that took a PC, and
returned the return address of the call represented by that PC, if the
instruction is a call?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-23 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 19:02 David Daney
2004-08-20 19:20 ` Theodore A. Roth
2004-08-23 17:14 ` Andrew Cagney
2004-08-23 18:04 ` David Daney
2004-08-23 18:26 ` Andrew Cagney
2004-08-23 18:42 ` David Daney
2004-08-23 18:48 ` Daniel Jacobowitz
2004-08-23 19:01 ` David Daney
2004-08-23 19:22 ` Daniel Jacobowitz [this message]
2004-08-24 19:29 ` Andrew Cagney
2004-08-23 19:05 ` Michael Chastain
2004-08-23 19:19 ` David Daney
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=20040823192159.GA12007@nevyn.them.org \
--to=drow@false.org \
--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