Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Cagney <cagney@gnu.org>,  gdb@sources.redhat.com
Subject: Re: Unable to step over (n and ni) on mipsel-linux...
Date: Mon, 23 Aug 2004 19:01:00 -0000	[thread overview]
Message-ID: <412A3E3F.3020409@avtrex.com> (raw)
In-Reply-To: <20040823184801.GA10657@nevyn.them.org>

Daniel Jacobowitz wrote:
>>>>Instead of stepping into a function and checking to see if we are in a
>>>>different frame (settting a breakpoint at the return address location),
>>>>why not set the breakpoint at the return location before making the
>>>>function call?
>>>
>>>
>>>That would mean examining every instruction to determine if it is a call 
>>>- effectively s/w single step.  GDB tries to do avoid doing that so that 
>>>single-step is faster.
>>>
>>
>>For my configuration, for some reason it is already doing this.  Thus my
>>comment.  If we are doing s/w single step, we would not have to examine
>>the stack frames.
>>
>>Could there are some configuration problems?
> 
> 
> GDB already does this on all MIPS targets.
> 
> 
>>This implies that if I write assembly language I cannot expect GDB's ni
>>instruction to work.
> 
> 
> It should work OK.  You have to have some stack frame anyway, and GDB
> has a prologue analyzer.
> 

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.

David Daney.



  reply	other threads:[~2004-08-23 19:01 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 [this message]
2004-08-23 19:22             ` Daniel Jacobowitz
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=412A3E3F.3020409@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=cagney@gnu.org \
    --cc=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