| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
but don't resolve localhost to ::1 (and vice versa for IPv4 and 127.0.0.1).
|
|\
| |
| |
| | |
PipeWatchProc(). When we are interested in both readable and writable events of a command pipeline channel, we only want the readable from the read end of the pipe, and the writable from the write end of the pipe.
|
| |
| |
| |
| |
| | |
PipeWatchProc(). When we are interested in both readable and writable
events of a command pipeline channel, we only want the readable from
the read end of the pipe, and the writable from the write end of the pipe.
|
|\ \
| |/
| |
| | |
the flag BUFFER_READY.
|
| |\
| | |
| | | |
of the flag BUFFER_READY.
|
| | | |
|
| | |
| | |
| | | |
BUFFER_READY flag serves no necessary purpose, so it is removed.
|
| | | |
|
| | |
| | |
| | |
| | | |
the OS networking machinery gets backed up and blocks.
Added several TODO comments on potential simplifications.
|
| |/ |
|
| | |
|
|\ \
| |/
| |
| |
| | |
platforms into the trunk. For details see the merged revision and its
ancestor.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
regarding the handling of wrapped dynamic libraries.
The basic flow of operation is to copy such libraries into a temp
file, hand them to the OS loader for processing, and then to delete
them immediately, to prevent them from being accessible to other
executables. On platforms where that is not possible the library is
left in place and things are arranged to delete it on regular process
exit.
An example of the latter are older revisions of HPUX which report that
the file is busy when trying to delete it. Younger revisions of HPUX
have changed to allow the deletion, but are also buggy, the OS loader
mangles its data structures so that a second library loaded in this
manner fails.
More recently it was found that Linux which is usually ok with
deleting the file and gets everything right shows the same trouble as
modern HPUX when the "docker" containerization system is involved, or
more specifically the AUFS in use there. Deleting the loaded library
file mangles data structures and breaks loading of the following
libraries. For a demonstration which does not involve Tcl at all see
the ticket
https://github.com/dotcloud/docker/issues/1911
in the docker tracker.
This of course breaks the use of wrapped executables within docker
containers.
This commit introduces the function TclSkipUnlink() which centralizes
the handling of such exceptions to unlinking the library after unload,
and provides code handling the known cases. IOW HPUX is generally
forced to not unlink, and ditto when we detect that the copied library
file resides within an AUFS.
The latter must however be explicitly activated by setting the define
-DTCL_TEMPLOAD_NO_UNLINK during build. We still need proper configure
tests to set it on the relevant platforms (i.e. Linux).
The AUFS detection and handling can be overridden by the environment
variable TCL_TEMPLOAD_NO_UNLINK which can force the behaviour either
way (skip or not). In case the user knows best, or wishes to test if
the problem with AUFS has been fixed.
|
| | |
|
| |
| |
| |
| | |
[dict create] to explicitly state that it returns the new dictionary.
|
| | |
|
| |
| |
| |
| | |
value.
|
| | |
|
| | |
|
| | | |
| \ | |
|\ \ \
| | |/
| | |
| | | |
particular not allowing them to leak between multiple layers of a stacked channel. Much common code refactored into ChanRead().
|
| | |\
| | | |
| | | |
| | | | |
particular not allowing them to leak between multiple layers of a stacked
channel. Much common code refactored into ChanRead().
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
What happened is that now that EOF flags no loger leak acros channel
stack layers, an EOF in the bottom channel isn't detected in the top one
until the ChanRead call at the top level actually returns 0 bytes. This
causes one more query/ma
|
| | | | |
|
| | | | |
|
| | | |\
| | | |/
| | |/| |
|
| | | |
| | | |
| | | | |
parts of the channel read machinery.
|
| | | |\ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
direct clearing of CHANNEL_EOF flag.
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
longer leaking across channel stacks.
|
| | | | | |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | |_|_|/ /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
began repairing some of the logic about them. Tests iogt-2.* now fail because
they've been crafted as experiments recording the fine detail of reflected
channel driver calls, and fixing the management of channel flags is changing
that. zlib-8.5 also needed adjustment to reflect that an EOF set must come
with an empty string read when flags are functioning properly.
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Refactored much management of the BLOCKED and EOF flags into ChanRead()
then began repairing some of the logic about them.
Tests iogt-2.* now fail because they've been crafted as experiments recording
the fine detail of reflected channel driver calls, and fixing the management
of channel flags is changing that.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Constrain them as "knownBug" rather than "unknownFailure".
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
io-35.18b - knownBug is not buggy on this branch.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
and refactor.
|
|\ \ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Windows where it makes sense.
* Rework WaitForConnect once more to always report ENOTCONN on I/O operations on failed async sockets.
* Fix synchronous connections to a server that only listens on IPv6 (or whatever comes later in the list returned by getaddrinfo(), socket-15.*)
* Fix spurious writable event on async sockets (socket-14.15).
|