Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Fixed TakeCommand exits upon "set [" command

Phileosophos

Phileosophos

Aug
197
5
I found this completely by accident when I mistyped a command as follows:

set [
Click to expand...

That causes the latest version of TakeCommand (TCC 14.02.42 x64 Windows 7 [Version 6.1.7601]
TCC Build 42 Windows 7 Build 7601 Service Pack 1) to exit immediately. I can't imagine it's a valid command to begin with but more graceful behavior is probably warranted.
 
Verified in
TCC 14.02.41 Windows XP [Version 5.1.2600] - 32b
(according to another thread B42 did not offer anything for those using 32b WinXP).
 
TCMD.gpf contains
Code: 
TCC  14.02.41 x64
Module=C:\Program Files\JPSoft\TCMD\TakeCmd.dll
Address=1002557E
Exception=C0000005
RX=00000001  RBX=00000000  RCX=0173FEF8  RDX=FFFFFFFF
RSI=00000000  RDI=00000000  RBP=016FE650  RSP=016FE5B0
CS=00000033  DS=0000002B  ES=0000002B  SS=0000002B
Flags=00010286
 
Stack:
1 : TakeCmd.dll 000000001002557e
2 : TakeCmd.dll 000000001002425c
3 : TakeCmd.dll 00000000100217b0
4 : TakeCmd.dll 00000000100ad20a
5 : TakeCmd.dll 00000000100acc8a
6 : TakeCmd.dll 00000000100ac8c8
7 : tcc.exe 000000000040427f
8 : tcc.exe 0000000000407a33
 
Phileosophos said:
I found this completely by accident when I mistyped a command as follows:



That causes the latest version of TakeCommand (TCC 14.02.42 x64 Windows 7 [Version 6.1.7601]
TCC Build 42 Windows 7 Build 7601 Service Pack 1) to exit immediately. I can't imagine it's a valid command to begin with but more graceful behavior is probably warranted.
Click to expand...
Here, Win7/SP1, it causes the "TCC has stopped working" dialog. There's no GPF file, but Windows reports this.
Code: 
Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    tcc.exe
  Application Version:    14.0.2.41
  Application Timestamp:    507769d5
  Fault Module Name:    tcc.exe
  Fault Module Version:    14.0.2.41
  Fault Module Timestamp:    507769d5
  Exception Code:    c0000005
  Exception Offset:    000035d6
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    44af
  Additional Information 2:    44afd2ce1d1421560c7c2722a5a3a421
  Additional Information 3:    9d26
  Additional Information 4:    9d26fada436710aa5d75968b8ab1706d
 
Here, under WinXP SP3 / 32b, TCC 14.02.41, there is no Windows message, no .GPF, and TCEXIT is not executed (or at least it does not get a chance to add a line to my usage log indicating the type of termination (from _EXIT).
 
rconn said:
Fixed in build 43.
Click to expand...
It still does it here; no GPF file.

Code: 
  Problem Event Name:    APPCRASH
  Application Name:    tcc.exe
  Application Version:    14.0.2.43
  Application Timestamp:    5080a5cb
  Fault Module Name:    tcc.exe
  Fault Module Version:    14.0.2.43
  Fault Module Timestamp:    5080a5cb
  Exception Code:    c0000005
  Exception Offset:    000035d6
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    44af
  Additional Information 2:    44afd2ce1d1421560c7c2722a5a3a421
  Additional Information 3:    9d26
  Additional Information 4:    9d26fada436710aa5d75968b8ab1706d
 
Code: 
C:\>ver

TCC  14.02.43   Windows XP [Version 5.1.2600]

C:\>set [
TCC: Not in environment "[*"

C:\>set [=foo

C:\>set [
foo

C:\>unset [

C:\>set [
foo

C:\>

The SET doesn't have any issue here. The UNSET doesn't remove the variable; because it interprets the bracket as the start of a wildcard sequence?
 
I get the same results as Charles with build 43 x64. Windows 7 Ultimate x64.
 
rconn said:
You might try reinstalling -- I uploaded the 32-bit build twice within a few minutes (the first time it had a couple of components that hadn't updated properly). It's possible you got a cached copy of the first upload.
Click to expand...
That must have been it. I uninstalled and re-installed from a freshly downloaded copy and now it's working OK.
 
You must log in or register to reply here.
Back
Top