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, 27 Oct 2005 18:08:00 -0000 [thread overview]
Message-ID: <20051027180803.GA28952@nevyn.them.org> (raw)
In-Reply-To: <4360F674.6070606@lipowsky.de>
On Thu, Oct 27, 2005 at 05:47:00PM +0200, Efim Monjak wrote:
> Hier are protocols for case you describe.
> The trap signal is reseived after ctrl+c but it steps after it.
> remote_interrupt called
> remote_stop called
> Packet received: T050B:EC3D0040;0D:DC3D0040;0F:60010040;
Try not returning SIGTRAP here.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-27 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 15:47 Efim Monjak
2005-10-27 18:08 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 10:52 Efim Monjak
2005-11-03 10:42 Efim Monjak
2005-11-03 21:23 ` Daniel Jacobowitz
2005-10-31 13:56 Efim Monjak
2005-10-31 14:19 ` 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=20051027180803.GA28952@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).