Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: "nagaraju.m" <nagaraju.m@redpinesignals.com>
Cc: gdb@sourceware.org
Subject: Re: Re:next
Date: Tue, 07 Jul 2009 10:40:00 -0000	[thread overview]
Message-ID: <1246963207.2548.4.camel@thomas> (raw)
In-Reply-To: <4A4DFA77.60707@redpinesignals.com>

On Fri, 2009-07-03 at 18:02 +0530, nagaraju.m wrote:

> 	I am new new to gdb. Thanks for the useful information that you provided.
> 	I have tried as you suggested, i checked function prologue but it is defined properly.
> 
> 	In my code "step", "stepi" and "continue" are behaving normally.
> 	
> 	"next" issue is not only with my target it is with simulator also.
> 
> 	When i debugged it with gdb it is behaving correctly up to
> 
> 	"*if(!frame_id_eq (get_frame_id (get_current_frame ()), step_frame_id)
>      		&& frame_id_eq (frame_unwind_id (get_current_frame ()), step_frame_id))*"
>     	this condition in infrun file in gdb. After this *start* and *end* points are changing as a result it is simply single stepping.
> 
> 	I am not able to trace the issue for here...
> 
> 	Can you please show me the path to resolve this issue...

Hi Nagaraju,

This is the test for whether the code is stepping into a function. Could
you post the output when you run "next" after "set debug infrun 1".

The suspicion is that your frame unwinder is not working correctly.

HTH,


Jeremy

-- 
Tel:      +44 (1590) 610184
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   jeremy.bennett@embecosm.com
Web:     www.embecosm.com


  reply	other threads:[~2009-07-07 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 12:45 Re:next nagaraju.m
2009-07-07 10:40 ` Jeremy Bennett [this message]
2009-07-07 11:53   ` next nagaraju.m
2009-07-07 15:19     ` next Jeremy Bennett

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=1246963207.2548.4.camel@thomas \
    --to=jeremy.bennett@embecosm.com \
    --cc=gdb@sourceware.org \
    --cc=nagaraju.m@redpinesignals.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