v26 exception log gone crazy

May 20, 2008
11,411
99
Syracuse, NY, USA
I knew nothing of this until Windows popped up a low disk space warning.

Code:
c:\programdata\jp software\take command 26> d t*
2021-08-14  12:09 422,797,849,306  tcc.exception.log

The logging started like this:

Code:
[2021/08/14 11:23:15.760] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO
[2021/08/14 11:23:15.760] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO
[2021/08/14 11:23:15.760] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO

and ended like this (400+ GB later):

Code:
[2021/08/14 12:09:24.574] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO
[2021/08/14 12:09:24.797] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO
[2021/08/14 12:09:24.976] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FFD85B42157 - INT_DIVIDE_BY_ZERO

I re-ran all of today's commands that might have involved v26 and none caused any further logging.

Shouldn't TCC terminate or let me know when something like this happens?

Any ideas?
 
May 20, 2008
11,411
99
Syracuse, NY, USA
Those log lines are 127 Unicode characters long (254 bytes). That's 1664558461 lines in 44 minutes, or 630514 lines per second. I would have thought that impossible.
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
4,466
88
Albuquerque, NM
prospero.unm.edu
Mine looks like this:

Code:
C:\ProgramData\JP Software\Take Command 26>dir

 Volume in drive C is Windows      Serial number is 4408:76e6
 Directory of  C:\ProgramData\JP Software\Take Command 26\*

12/15/2020  13:16         <DIR>    .
12/15/2020  13:16         <DIR>    ..
11/17/2020   8:41         <DIR>    updates
12/15/2020  13:18           1,002  TCC.exception.log
               1,002 bytes in 1 file and 3 dirs    4,096 bytes allocated
     152,610,078,720 bytes free

C:\ProgramData\JP Software\Take Command 26>type TCC.exception.log
[2020/12/15 12:16:38.672] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FF931DD1000 - ACCESS_VIOLAT
ION
[2020/12/15 12:18:27.442] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FF931511000 - ACCESS_VIOLAT
ION
[2020/12/15 12:18:27.442] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FF931511000 - ACCESS_VIOLAT
ION
[2020/12/15 12:18:35.381] D:\TakeCommand26\tcc\ntinit.cpp:364 wmain()  SEH Exception: 0x00007FF931511000 - ACCESS_VIOLAT
ION

C:\ProgramData\JP Software\Take Command 26>

I'll bet I was working on a plugin that day. And doing something wrong.
 
May 20, 2008
11,411
99
Syracuse, NY, USA
All I did today that involved TCCv26 were variations of this theme.

Code:
do i=24 to 28 ( d:\tc%i\tcc.exe /c eval_alias 2+2 ^> clip: & echo ^%@clip[0] )
 

rconn

Administrator
Staff member
May 14, 2008
12,356
150
The exception logging is done in a separate (very minimal) thread that has no communication with the other TCC threads.

SEH exception logging is 99.99% plugins or apps that are injecting code into TCC. Exceptions that occur in TCC code are handled differently (not via SEH).
 
May 20, 2008
11,411
99
Syracuse, NY, USA
Hmmm! The only DLLs attached to TCCv26, other than system DLLs and DLLs from JPSoft, are my own plugins, which don't use SEH or do any injecting.

I don't suppose the OS knows anything about TCC's exception log. Is there any way the thread you spoke of can get "stuck" and log over 600,000 messages per second for 44 minutes?
 
Similar threads
Thread starter Title Forum Replies Date
S Issues with version v26.02.42 x64 Support 0
R Problem with @INT[ value] in V26 Support 9
Alpengreis Python support for 3.8.3 in TCC v26.x? Support 2
Peter Murschall TCC V26.01.3x Debugging has problems with Alias /R Support 1
Alpengreis Fixed [v26.00.26] Crash after answering INKEY with <Ctrl>+C Support 1
Peter Murschall V26-Issues in the BDEBUGGER ! Support 11
Alpengreis Remaining TCMD background process (v26) ... Support 19
Alpengreis WAD [v26 Beta RC3]: MSGBOX color problems Support 4
Alpengreis Fixed [v26 Beta RC2]: Crash after Options, Take Command, Advanced Support 6
rconn News Take Command / TCC / CMDebug / TCC-RT v26 Public Beta build 26.0.21 Support 0
rconn News Take Command / TCC / CMDebug v26 Public Beta Support 0
rconn Dropping Windows 7 support in Take Command / TCC v26 Support 8
Alpengreis Fixed Crash after copy dialog with big TCC.exception.log Support 5
DrusTheAxe Runaway TCC.exception.log filling drive Support 5
Joe Caverly tcc.exception.log Support 3
vefatica C0000005 exception unloading plugin? Support 6
vefatica Strange tcc.exception.log Support 7
Stefano Piccardi Fixed 13.01.31 software exception Support 0
vefatica Unhandled exception again Support 3
vefatica Unhandled exception Support 3
rps LOG /a (all) with Atl-F2 Support 2
C Documentation default location for LOG files Support 21
P LOG command behavior Support 3
rps How to? Alias/Command line use of *log on/off Support 2
C b34 Installer leaves LOG in %LocalAppData%\Temp\ Support 1
C LOG entry for TCMD/TCC command line Support 15
Jay Sage WAD Issues with LOG Command Support 4
vefatica TCC.LOG Support 4
D How to? How to show variables expanded in the log tab Support 3
M How to? Start a program on log on elevated abovenormal Support 5
F Dating a log Support 14
C TPipe Log file not correct Support 1
A How to? Set up a log file for all command output Support 3
vefatica aemail\datamystic.log? Support 1
M How to? Save the session log from a batch file? Support 5
S Documentation LOG command Support 0
dcantor Documentation Help error for command LOG Support 0
S Log and foldermonitor problems Support 3
S LOG within a batch file Support 1

Similar threads