public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Efim Monjak <ymonyak@lipowsky.de>
Cc: gdb@sources.redhat.com
Subject: Re: break of close loop
Date: Fri, 04 Nov 2005 14:27:00 -0000	[thread overview]
Message-ID: <20051104142702.GB1842@nevyn.them.org> (raw)
In-Reply-To: <436B2677.4020802@lipowsky.de>

On Fri, Nov 04, 2005 at 10:14:31AM +0100, Efim Monjak wrote:
> Hi,
> 
> as I see the step for debugger is not the same as stepi.
> After step command debugger try to go to the next source line.
> I think it checks for number of source line.
> I mean many single steps can be done before an another source
> line is recognised. Recognising of an other source line is need
> to complete the step command.
> After single step command only one single step is done. I don't know
> if for an other address is checked or single step responce is enougth
> to complete the single step.

Then your stub is simply wrong.  GDB expects a single step instruction
to execute a single instruction, not until the address changes.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-04 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04  9:15 Efim Monjak
2005-11-04 14:27 ` Daniel Jacobowitz [this message]
2005-11-04 15:13   ` Dave Korn
2005-11-04 15:19     ` Simon Richter
2005-11-04 15:35       ` Dave Korn
2005-11-04 15:39       ` 'Daniel Jacobowitz'
2005-11-04 15:46         ` Dave Korn
2005-11-04 16:00           ` 'Daniel Jacobowitz'
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 16:41 Efim Monjak
2005-11-03 21:25 ` Daniel Jacobowitz

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=20051104142702.GB1842@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ymonyak@lipowsky.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).