summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* merge trunkKevin B Kenny2014-06-2999-4107/+6146
|\
| * Fix mismatch of Tcl_Preserve() / Tcl_Release().dgp2014-06-261-2/+1
| |\
| | * Fix mismatch of Tcl_Preserve() / Tcl_Release().dgp2014-06-261-2/+1
| | |
| * | Simplify / refactor Tcl_ReadRaw(). No need for CopyBuffer().dgp2014-06-241-127/+50
| |\ \ | | |/
| | * Simplify / refactor Tcl_ReadRaw(). No need for CopyBuffer().dgp2014-06-241-127/+50
| | |
| * | Fix execute-6.5 test failure on trunk: the "preserveCore" part of ↵jan.nijtmans2014-06-231-33/+33
| |\ \ | | |/ | | | | | | tcltest::test assumes that the cleanup is done first, so moving the cleanup means the the "preserverCore" part needs to move with it.
| | * Fix execute-6.5 test failure on trunk: the "preserveCore" part of ↵jan.nijtmans2014-06-231-33/+33
| | | | | | | | | | | | tcltest::test assumes that the cleanup is done first, so moving the cleanup means the the "preserverCore" part needs to move with it.
| * | ticket [2f9df4c4fa]: tcltest - request to move -cleanup script execution ↵jan.nijtmans2014-06-224-14/+14
| |\ \ | | |/ | | | | | | | | | until after -output compare. tcltest -> version 2.3.8
| | * ticket [2f9df4c4fa]: tcltest - request to move -cleanup script execution ↵jan.nijtmans2014-06-224-14/+14
| | |\ | | | | | | | | | | | | | | | | until after -output compare tcltest -> version 2.3.8
| | | * previous commit was not quite right, this one should be betterjan.nijtmans2014-06-201-14/+14
| | | |
| | | * ticket [2f9df4c4fa]: tcltest - request to move -cleanup script execution ↵jan.nijtmans2014-06-204-12/+12
| | |/ | | | | | | | | | until after -output compare
| * | [b47b176adf] Stop possible segfaults when variability in mutex lockaku2014-06-201-0/+16
| |\ \ | | |/ | | | | | | | | | schedules cause a ForwardingResult to remain on the forwardList after it has been processed (IORChan is the origin of the code in IORTrans).
| | * [b47b176adf] Stop possible segfaults when variability in mutex lockaku2014-06-201-0/+16
| | | | | | | | | | | | | | | schedules cause a ForwardingResult to remain on the forwardList after it has been processed (IORChan is the origin of the code in IORTrans).
| * | [b47b176adf] Stop segfault when variability in mutex lock schedules cause dgp2014-06-191-0/+6
| | | | | | | | | | | | a ForwardingResult to remain on the forwardList after it has been processed.
| * | [f0f876c141] Improve consistency in error messages.dkf2014-06-1714-56/+58
| | |
| * | [1758a0b603] socket_*-2.13 : Workaround the broken select() in some Linuxdgp2014-06-161-2/+56
| |\ \ | | |/ | | | | | | kernels that fails to report a writable state on a socket when an error condition (or remote close) is present.
| | * [1758a0b603] socket-2.13 : Workaround the broken select() in some Linuxdgp2014-06-161-3/+58
| | |\ | | | | | | | | | | | | kernels that fails to report a writable state on a socket when an error condition (or remote close) is present.
| | | * merge 8.5dgp2014-06-161-0/+41
| | | |\ | | | |/ | | |/|
| | | * Additional check for an error condition on the socket.dgp2014-06-121-1/+7
| | | |
| | | * Workaround the broken select() in some Linux kernels that fails to reportdgp2014-06-111-3/+52
| | | | | | | | | | | | | | | | | | | | a writable state on a socket when an error condition (or remote close) is present. Would be good to add actual test suite tests for this, but until then see demo scripts in the ticket 1758a0b603.
| * | | merge socket test from 8.5dgp2014-06-161-0/+42
| |\ \ \ | | |/ /
| | * | Draft test for [1758a0b603].dgp2014-06-131-0/+41
| | |/
| * | [311e61d12a] Generate error code in *all* places where commands are looked up.dkf2014-06-161-1/+2
| | |
| * | [cb042d294e] Improve consistency of [dict] wrong-args error messages.dkf2014-06-153-41/+41
| | |
| * | [1b0266d8bb] Make [dict replace] and [dict remove] have canonicalization ↵dkf2014-06-154-161/+287
| |\ \ | | | | | | | | | | | | semantics close to [lrange] and [lreplace]. [dict merge] is also improved, but is not as strict.
| | * | Some more cleaning updkf2014-06-151-36/+44
| | | |
| | * | Make [dict replace] and [dict remove] guarantee result canonicality.dkf2014-06-152-95/+84
| | | |
| | * | Improved the error messages. dkf2014-06-074-39/+104
| | | | | | | | | | | | | | | | We do not want parsing an invalid dictionary to give errors about lists! As compensation, we get greater precision in the errorcode.
| | * | merge trunkdkf2014-06-063-5/+83
| | |\ \ | | |/ / | |/| |
| * | | Tests socket*-2.12 test for DiscardOutput() updates.dgp2014-06-051-1/+39
| |\ \ \ | | | |/ | | |/|
| | * | Test socket-2.12 covers the DiscardOutput() update.dgp2014-06-051-1/+39
| | | |
| * | | When too many chars are read by ReadChars() and we trim the limits to get it ↵dgp2014-06-052-4/+44
| |\ \ \ | | |/ / | | | | | | | | right on the next pass, don't forget the TCL_UTF_MAX padding demanded by Tcl_ExternalToUtf(). (Thanks for finding that, aku!) Fix the factorPtr management. It was just totaly wrong. The factor should be a ratio of the record of bytes read to the record of chars read. With those fixes, new test io-12.6 covers the "too many chars" code.
| | * | merge forkdgp2014-06-050-0/+0
| | |\ \
| | | * | Fixed a tricky interaction of IO system and encodings which couldandreask2014-06-051-2/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | result in a panic. The relevant function is ReadChars() (short RC in the following). When the encoding and translation transforms deliver more characters than were requested the iterative algorithm used by RC reduces the value of "dstLimit" (= the number of bytes allowed to be copied into the destination buffer) to force the next round to deliver less characters, hopefully the number requested. The existing code used the byte located just after the last wanted character to determine the new limit. The resulting value could _undershoot_ the best possible limit because Tcl_ExternalToUtf would effectively reduce this limit further, by TCL_UTF_MAX+1, to have enough space for a single multi-byte character in the buffer, and a closing '\0' as well. One effect of this were additional calls to ReadChars() to retrieve the characters missed by a call with an undershot limit. In the limit (sic) however this was also able to cause a full-blown "Buffer Underflow" panic if the original request was for less than TCL_UTF_MAX characters (*), and we are using a single-byte encoding like iso-8859-1. Because then the undershot dstLimit would prevent the next round from copying anything, and causing it to try and consolidate the current buffer with the next buffer, thinking that it had to merge a multi-byte character split across buffer boundaries. (Ad *) For example because the previous call had undershot already and left only such a small amount of characters behind! The basic fix to the problem is to add TCL_UTF_MAX back to the limit, like is done in all the (three) other places in RC setting a new one. Note however that this naive fix may generate a new limit which is the same as the old, or possibly larger. If that happens we act very conservatively and reduce the limit by only one byte instead. While I believe that this last conservative approach will never reduce the limit to TCL_UTF_MAX or less before reaching a state where it returnds the exact amount of requested characters I still added a check against this situation anyway, causing a new panic if triggered.
| | * | | When too many chars are read by ReadChars() and we trim the limits todgp2014-06-052-4/+44
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | get it right on the next pass, don't forget the TCL_UTF_MAX padding demanded by Tcl_ExternalToUtf(). (Thanks for finding that, aku!) Fix the factorPtr management. It was just totaly wrong. The factor should be a ratio of the record of bytes read to the record of chars read. With those fixes, new test io-12.6 covers the "too many chars" code.
| | | * merge trunkdkf2014-06-064-15/+29
| | | |\ | | |_|/ | |/| |
| * | | Add missing calls to Tcl_DecrRefCount() in string object man page examples.andy2014-06-041-1/+4
| | | |
| * | | Revise DiscardOutput() to account for revisions to the loop in ↵dgp2014-06-041-0/+5
| |\ \ \ | | |/ / | | | | | | | | FlushChannel() which is its only caller. We need to discard the curOutPtr buffer as well, and not count on another pass through the loop to attempt to flush it (and raise the same failure again?).
| | * | Revise DiscardOutput() to account for revisions to the loop in FlushChannel()dgp2014-06-041-0/+5
| | | | | | | | | | | | | | | | | | | | which is its only caller. We need to discard the curOutPtr buffer as well, and not count on another pass through the loop to attempt to flush it (and raise the same failure again?).
| | * | merge fork of 8.5 branchdgp2014-06-034-27/+42
| | |\ \
| * | | | Valgrind doesn't like use of uninitialized variables.dgp2014-06-041-1/+1
| | | | |
| | | | |
| | \ \ \
| *-. \ \ \ [734138ded8] Revisions so that unreported errors don't get lost duringdgp2014-06-033-13/+19
| |\ \ \ \ \ | | | | |/ / | | | |/| | the close of a channel.
| | | * | | Backport I/O core fixes made known by async socket work on trunk.dgp2014-06-031-7/+15
| | | |\ \ \ | | | |/ / / | | |/| | |
| | * | | | These edits make all tests outside of socket-14.* pass on OSX Mavericks.dgp2014-06-031-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | Several socket-14.* tests failing there, and those that pass are very slow about it. Firewall or poor networking configuration may be playing a role.
| | * | | | These edits make the tests socket-14.11.[01] stop hanging, but also introducedgp2014-06-023-12/+16
| |/ / / / | | | | | | | | | | a whole raft of test failures. WIP.
| | * | | win socket -async: do not loose connect notification by temporarily stop ↵oehhar2014-05-301-6/+14
| | |\ \ \ | | | | | | | | | | | | | | | | | | connect monitoring. Bug [336441ed59]
| | | * | | Try not to loose FD_CONNECT by switching monitoring off.oehhar2014-05-291-5/+9
| | | | | |
| | | * | | merge core-8-5-branchoehhar2014-05-2938-1664/+2195
| | | |\ \ \ | | | |/ / / | | |/| | |
| | | | | * more tests, cleaning up the code a bitdkf2014-06-042-16/+42
| | | | | |
| | | | | * merge trunkdkf2014-06-031-60/+75
| | | | | |\ | | |_|_|_|/ | |/| | | |
generated by cgit v0.12 at 2024-11-17 14:07:28 (GMT)