From: SourceForge.net <no...@so...> - 2008-12-22 18:30:51
|
Bugs item #2446662, was opened at 2008-12-19 03:41 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=2446662&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 25. Channel System Group: development: 8.6a4 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin B KENNY (kennykb) Assigned to: Andreas Kupries (andreas_kupries) Summary: chanIO.test failures on Win32 msys/mingw Initial Comment: On the msys/mingw build on Windows, 'make test' gives: ==== chan-io-28.7 Tcl_CloseEx (half-close) socket FAILED ==== Contents of test case: set echo [makeFile { proc accept {s args} {set ::sok $s} set s [socket -server accept 0] puts [lindex [fconfigure $s -sockname] 2] flush stdout vwait ::sok fconfigure $::sok -buffering line while {[gets $::sok line]>=0} {puts $::sok $line} puts $::sok DONE exit 0 } echo.tcl] set ::ff [open "|[list [interpreter] $echo]" r] gets $::ff port set ::s [socket 127.0.0.1 $port] puts $::s Hey close $::s w set timer [after 1000 {set ::done Failed}] set ::acc {} fileevent $::s readable { if {[gets $::s line]<0} { set ::done Succeeded } else { lappend ::acc $line } } vwait ::done after cancel $timer close $::s r close $::ff list $::done $::acc ---- Result was: Succeeded {} ---- Result should have been (exact matching): Succeeded {Hey DONE} ==== chan-io-28.7 FAILED ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-12-22 18:30 Message: Could well be, though the google example is no proof (here the HTTP server must be doing some optimization to resist attacks). Still trying to pinpoint it. Windows' unability to wireshark on loopback interface is a nightmare... Do you know of an alternative ? Or a public echo server ? ---------------------------------------------------------------------- Comment By: Andreas Kupries (andreas_kupries) Date: 2008-12-22 17:29 Message: Oh, could this be where Windows, the OS, is fast-tracking the close operation, discarding buffered data ? IIRC this was trouble for something else as well. I do not recollect details however :( ---------------------------------------------------------------------- Comment By: Alexandre Ferrieux (ferrieux) Date: 2008-12-21 18:44 Message: Getting closer I think :-) The following code: set s [socket www.google.fr 80];puts $s "GET / HTTP/1.0\n";close $s w;after 1000;puts [read $s];close $s consistently displays en empty line. I have the impression that it shouldn't. (Am I right ?) Wireshark says that a FIN is sent after the GET, and that google responds by another FIN with no data. Have to check the RFC again to check why the Windows shutdown() does that bad variant of FIN. ---------------------------------------------------------------------- Comment By: Alexandre Ferrieux (ferrieux) Date: 2008-12-20 12:12 Message: Oh, now I can again with HEAD. Heisenbug.. race condition ? ---------------------------------------------------------------------- Comment By: Alexandre Ferrieux (ferrieux) Date: 2008-12-19 17:41 Message: Kevin, are you still seeing it ? Cannot seem to repro. ---------------------------------------------------------------------- Comment By: Andreas Kupries (andreas_kupries) Date: 2008-12-19 05:14 Message: 2444274 is a gob of multiple problems. My changes fixed the underlying flush handling in the generic IO layer. dgp's changes, as I understood it, prevent the test cases from writing errorInfo contents to stderr, causing the chanio.test reported as exiting with error, for -singleproc 0. ---------------------------------------------------------------------- Comment By: Kevin B KENNY (kennykb) Date: 2008-12-19 04:52 Message: For what it's worth, this happened *after* dgp committed changes purporting to fix 2444274 ---------------------------------------------------------------------- Comment By: Andreas Kupries (andreas_kupries) Date: 2008-12-19 04:38 Message: Yes, see the latest comments at https://sourceforge.net/tracker2/index.php?func=detail&aid=2444274&group_id=10894&atid=110894 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=2446662&group_id=10894 |