Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kishore Paul <kishorep@freescale.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: vCont packets for next and step
Date: Mon, 12 Feb 2007 22:07:00 -0000	[thread overview]
Message-ID: <45D0E31E.8030802@freescale.com> (raw)
In-Reply-To: <20070212214040.GA23093@caradoc.them.org>

Should the gdb host not be sending multiple vCont step packets for next, 
just like it does for step?

Thanks,
Kishore

Daniel Jacobowitz wrote:

>On Mon, Feb 12, 2007 at 03:36:26PM -0600, Kishore Paul wrote:
>  
>
>>Hi All,
>>
>>How does the gdb next and step work? I am seeing a problem where next 
>>only sends one vCont packet, similar to stepi though I was expecting a 
>>set of vCont packets to be sent similar to a step.
>>    
>>
>
>That means that, after the single stepi, the "next" thinks it has
>reached a different source line.  So it stops.
>
>  
>


  reply	other threads:[~2007-02-12 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 21:42 Kishore Paul
2007-02-12 21:50 ` Daniel Jacobowitz
2007-02-12 22:07   ` Kishore Paul [this message]
2007-02-13  3:06     ` Daniel Jacobowitz
2007-02-13  3:25     ` 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=45D0E31E.8030802@freescale.com \
    --to=kishorep@freescale.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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