tcc.exe /c whatever/... triggers debug messages

[Daniel Dittmar]

TCC 27.01.24 x64

TCC.EXE /c whatever/... triggers a sequence of message boxes, which I assume are for jpsoft internal development purposes

1. GetCommandLine()=<path>TCC.EXE /c whatever/...
2. OLE & COM Initialization
3. Initialize global variables
4. Initialize system variables
5. Parsing command line (/c whatever/...)

This happens when there is a /... anywhere in the command line.

This occured in Python code
os.system ('p4 sync somedir/...')
where os.system spawns a new command processor and ... is a wildcard and can't be replaced by anything else.

I found a workaroud
set DOTS=...
os.system ('p4 sync somedir/%DOTS%')

 

[rconn]

WAD - TCC interprets a "/..." argument as a startup debugging request. (I had to pick something to do that, and I'd never seen anybody use /... as an actual argument!)

 

[Daniel Dittmar]

Thanks for the reply. As I wrote, there is a workaround at least in my case, so for the time being, I can live with it.