public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "daney at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/15430] Cannot interrupt blocking I/O calls with close()
Date: Wed, 09 Nov 2005 17:46:00 -0000	[thread overview]
Message-ID: <20051109174632.20180.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15430-6651@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from daney at gcc dot gnu dot org  2005-11-09 17:46 -------
Created an attachment (id=10189)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10189&action=view)
Program that demonstrates how shutdown can solve the problem.

Compile socktest.c thusly:

gcc -g -o soctest soctest.c -lpthread

Then run it and from a different window telnet localhost 4455

Do not type anything in the telnet window.

When the socket is shutdown the read returns with a value of zero.

I guess we should shutdown as well as close in the socket code.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15430


       reply	other threads:[~2005-11-09 17:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15430-6651@http.gcc.gnu.org/bugzilla/>
2005-11-09 17:46 ` daney at gcc dot gnu dot org [this message]
2005-11-09 18:22 ` aph at gcc dot gnu dot org
2005-11-09 19:24 ` daney at gcc dot gnu dot org
2005-11-10  0:34 ` daney at gcc dot gnu dot org
2005-11-15 19:11 ` daney at gcc dot gnu dot org
2005-11-15 19:16 ` daney at gcc dot gnu dot org
2005-11-25 19:10 ` guilhem at kaffe dot org
2004-05-14  1:23 [Bug libgcj/15430] New: " mckinlay at redhat dot com
2004-05-14  1:26 ` [Bug libgcj/15430] " mckinlay at redhat dot com
2004-05-14  1:29 ` pinskia at gcc dot gnu dot org
2004-08-14  6:59 ` pinskia at gcc dot gnu dot org
2005-01-15 22:30 ` konqueror at gmx dot de

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=20051109174632.20180.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).