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 time loop
Date: Thu, 03 Nov 2005 21:23:00 -0000	[thread overview]
Message-ID: <20051103212350.GB11828@nevyn.them.org> (raw)
In-Reply-To: <4369E990.9060305@lipowsky.de>

On Thu, Nov 03, 2005 at 11:42:24AM +0100, Efim Monjak wrote:
> Hi all,
> 
> is there a particular time between send a "step" command and ctrl+c.

No, the ctrl-c is processed whenever GDB receives it from the user, if
the target is running.

> I see the ctrl+c charakter on different place depend on performanse of 
> target.
> If I set a big delay before send "step" response I see about 1 sec. 
> between "step" command
> and ctrl+c. Signal Interrupt which stops the time loop after ctrl+c 
> don't stops
> the loop if ctrl+c is received after "stop" response but to close to 
> next "step"
> command to send a special responce to ctrl+c. In this case next "step" 
> is responced
> with interrupt signal. But the loop will not be stopped.

Sorry, I can not follow the situation you are describing.  I would need
to see an example session.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-03 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 10:42 Efim Monjak
2005-11-03 21:23 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-04 10:52 Efim Monjak
2005-10-31 13:56 Efim Monjak
2005-10-31 14:19 ` Daniel Jacobowitz
2005-10-27 15:47 Efim Monjak
2005-10-27 18:08 ` Daniel Jacobowitz
2005-10-27 15:19 Efim Monjak
2005-10-27 15:23 ` Daniel Jacobowitz
2005-10-27 14:04 Efim Monjak
2005-10-27 14:34 ` 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=20051103212350.GB11828@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).