Strange tcc.exception.log

May 20, 2008
Syracuse, NY, USA
I don't remember what I was doing at 23:54 on 2017-04-18, but at that time I got a strange tcc.exception.log. It's strange because
(1) it's in "c:\ProgramData\JP Software\Take Command 21". Normally exception logs go into TCC's home directory.
(2) it's 19 MB with 92,243 lines, all but the first lines being identical except for the time stamp. Here are the first, second, and last lines.
[2017/04/18 23:52:39.226] ..\tcc\ntinit.cpp:346 wmain()  SEH Exception: 0x5D77C876 - ACCESS_VIOLATION
[2017/04/18 23:52:39.226] ..\tcc\ntinit.cpp:346 wmain()  SEH Exception: 0x5D77E159 - ACCESS_VIOLATION
[2017/04/18 23:53:21.206] ..\tcc\ntinit.cpp:346 wmain()  SEH Exception: 0x5D77E159 - ACCESS_VIOLATION

The file is stamped 23:54, a little odd since its last line is stamped 23:53:21.

The file is Unicode but has no BOM (normal?). HEAD. TAIL, and TYPE all choke on it. In the same directory is a tcmd.exception.log, empty except for a BOM.

Is there a sure-fire way to get TCC to write an exception log? I'd like to test where it actually goes.


Staff member
May 14, 2008
The exception log in v21 is written to \programdata to avoid permission problems when writing to \program files.

TCC *always* writes an exception log at startup. It's empty (other than a BOM) until an internal (fatal) exception occurs. But 99% of the exceptions these days are coming from Windows or third-party injected dll's, so it's rare to actually get an exception log that contains anything.

In your log file, something else (not TCC) is throwing the exception; TCC is catching it & logging it.
May 20, 2008
Syracuse, NY, USA
I just tested several times. If tcc.exception.log does not exist, TCC creates it without a BOM; likewise tcmd.exception.log. moments ago, I deleted both with v20 and started TCMD21.
May 20, 2008
Syracuse, NY, USA
No. The log file is created with a BOM; but you're looking at an open file that Windows hasn't updated the directory entry for yet. Close the TCMD session and you'll see the files are 2 bytes with a BOM.
The file I mentioned at the beginning of this thread did not have a BOM.
Similar threads
Thread starter Title Forum Replies Date
M Strange error messages from TCC in FTP copy Support 7
R strange bug? Support 7
Jesse Heines Strange Line Wrapping Behavior Support 14
F strange results Support 9
M Another possibly strange remote registry issue Support 5
forbin Strange handling of [nonbright] magenta background (v22) Support 2
N Fixed Strange dir behavior Support 6
vefatica REGDIR, strange error message Support 7
T WAD Strange Unexpected "features" in the Debugger Support 2
P Strange mouse behavior with list Support 2
vefatica A strange one Support 0
D Strange DO behavior with /O Support 5
Glenn Bowes Strange text at startup Support 5
Steve Pitts WAD Strange output from DEL of a non-existent directory Support 7
vefatica Big numbers, strange errors Support 1
aedthuio Strange... lpksetup Support 4
CWBillow dir /4 strange Support 2
D Strange issue with FOR loop Support 15
MikeBaas Strange prob with %@replace.. Support 4
vefatica OT: strange files in %TEMP Support 10
Dan Glynhampton Documentation v15 help: Strange links in @INT topic Support 0
R WAD Strange output from "memory" command Support 1
M Yet another strange something re something called "@TCONVERT" Support 8
Roedy How to? Strange colours Support 9
M WAD Strange "Start" misbehavior... Support 10
vefatica Very strange console font corruption Support 3
Steve Pitts Strange problem with FREE Support 10
A strange error in alias Support 9
newgeekorder Debugger IDE - strange tab and parameter behaviour Support 1
Exolon Strange Prompt. Support 6
vefatica Strange folders Support 1
T Strange CPU value Support 3
J Strange error: unset /s Support 14
M Strange behavior... Support 2
CWBillow Strange happenings Support 2
B Strange handling of a .BAT file Support 5
vefatica Strange behavior reloading SHRALIAS sav files. Support 1
J ASSOC / FTYPE strange error message Support 3
D Strange crashes in @CRC32 and @MD5 Support 9
Charles Dye Strange output, here-doc redirection, TYPE, //UnicodeOutput=Yes Support 6
S Strange CHKDSK behavior Support 6
vefatica Strange results with CP 1252 Support 12
S Strange REN problem - non-English characters Support 3
dcantor Strange status in ACTIVATE command Support 0
vefatica TCC startup: /IP not honored after /K Support 1
MickeyF TCC crashing when copying multiple files (now resolved) Support 6
C COMSPEC constantly reset to TCC.EXE Support 6
rconn News Take Command / TCC / CMDebug / TCC-RT v28 Released Support 0
C How to? starting TCC/TCMD v25 Support 2
CWBillow TCC and TCMD in Powershell Support 6

Similar threads