Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Roland.Puntaier@br-automation.com, gdb@sourceware.org
Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C
Date: Wed, 22 Aug 2007 03:13:00 -0000	[thread overview]
Message-ID: <ubqd0w9c3.fsf@gnu.org> (raw)
In-Reply-To: <m3ejhw4fil.fsf@codesourcery.com> (message from Jim Blandy on 	Tue, 21 Aug 2007 16:46:58 -0700)

> Cc: Roland.Puntaier@br-automation.com,  gdb@sourceware.org
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 21 Aug 2007 16:46:58 -0700
> 
> >> The issue at hand here is that we need C-c to interrupt the main
> >> thread as it reads from the remote host.  That could be a pipe, a
> >> socket, or a serial port.
> >> 
> >> Do you know how one can safely interrupt each of these kinds of reads
> >> in Windows?
> >
> > What do you mean by ``safely interrupt''?
> 
> The main thread is in the midst of a 'read' or 'write' operation.  We
> want the thread handling the C-c to be able to make the main thread
> abandon that operation with a suitable indication of why.

Maybe I'm simply unaware of some subtle issues, but I don't know of
any situation where this cannot be done safely.  In particular, the
code I wrote for GNU Make works since the release of Make 3.81, and I
have yet to see any problems with interrupting a running Make, or hear
a single complaint or bug report related to C-c.


  reply	other threads:[~2007-08-22  3:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 16:20 Roland Puntaier
2007-08-20 16:24 ` Daniel Jacobowitz
2007-08-20 19:16   ` Eli Zaretskii
2007-08-20 19:31     ` Daniel Jacobowitz
2007-08-21  2:56       ` Christopher Faylor
2007-08-21 17:42         ` Jim Blandy
2007-08-21 19:09           ` Eli Zaretskii
2007-08-21 23:47             ` Jim Blandy
2007-08-22  3:13               ` Eli Zaretskii [this message]
2007-08-22 10:13                 ` Dave Korn
2007-08-22 19:17                   ` Eli Zaretskii
2007-08-24  9:19                     ` Roland Puntaier
2007-08-24 16:12                     ` Roland Puntaier
2007-08-21 22:55           ` Christopher Faylor
2007-08-22 11:10         ` Roland Puntaier
2007-08-22 19:20           ` Eli Zaretskii
2007-08-23  2:49             ` 答复: (Rising Spam Alert)Re: " xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
2007-08-23  2:49             ` xchen
     [not found]             ` <NUTMEGt3HvoFOAmEaJs0000003d@mail.artimi.com>
2007-08-23  9:30               ` Dave Korn
2007-08-21  3:22       ` Eli Zaretskii

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=ubqd0w9c3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Roland.Puntaier@br-automation.com \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.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