Tcl Source Code

View Ticket
Login
Ticket UUID: 537f9f98f410a442eb945aaa9cb163e4ef0b9837
Title: windows handling "entry point not found" exception
Type: Bug Created on: 2014-06-23 19:14:23
Submitter: dgp Assigned to: nobody
Subsystem: 27. Channel Types Severity: Minor
Priority: 5 Medium Last modified: 2014-06-23 19:14:23
Status: Open Closed by: nobody
Resolution: None Closed on:
Version:
Description:
dgp	http://core.tcl.tk/tcl/info/e69a0476efd6b58dbd9cbb23631ea18f13fc114d
dgp	Looks like this checkin introduced a bug to me.
dgp	The code changes certainly changed behavior, while the comment remains the same.
dgp	line 2625.
dgp	The upshot is that [exec $program] in Tcl will report a number of program ending exceptions in $program ....
dgp	notably, at least some failures of [load]ing libraries....
dgp	..as "child killed: unknown signal"
dgp	because the actual exit code matched the magic 0xC0000000 pattern Tcl_WaitPid is crafting.
aku	0xC0... is, I believe the 2 MSB bits of the value (assuming a 32bit int)

dgp	on at least some DLL load failures that crash $program, the exit code is 0xc0000139
dgp	http://stackoverflow.com/questions/8908112/the-specified-procedure-could-not-be-found-error-when-running-app-on-windows-x
dgp	I presume the "Entry Point not found" exception could be added to the list of exceptions given special processing by the win implementation of Tcl_WaitPid() ?