This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Unable to step over (n and ni) on mipsel-linux...


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.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]