'bad code' in tcl file command
Martin M. Hunt
hunt@redhat.com
Fri Feb 7 04:28:00 GMT 2003
Jeff,
Thanks for catching this. There is a problem with high levels of
optimization and some inline assembly code. I will check in a fix as
soon as I am finished testing to make sure nothing else got broken.
Martin
On Wed, 2003-02-05 at 18:13, Jeff Mincy wrote:
>
>
> The latest tcl 8.4 gets 'command returned bad code' errors when doing
> the file copy and file rename commands. Other than the 'bad code'
> errors which have to be caught, the file commands appear to work correctly.
>
> Here is sample output:
>
> ================
> bash% rm -r -f foo bar baz
>
> bash% which tclsh84
> /usr/bin/tclsh84
>
> bash% echo "foo bar" >> foo
>
> bash% cat foo
> foo bar
>
> bash% tclsh84
> =================
>
> puts [file copy foo bar]
> command returned bad code: 269325160
>
> puts $errorInfo
> command returned bad code: 269325160
> while executing
> "puts [file copy foo bar]"
>
> puts [file rename bar baz]
> command returned bad code: 269325832
>
> puts $errorInfo
> command returned bad code: 269325832
> while executing
> "puts [file rename bar baz]"
>
> exit
> ================
>
> I am on w98, running the latest cygwin.
>
> -jeff
>
More information about the Insight
mailing list