TCC/LE 13.06.77 64-bit won't start

[Maximus5]

Originally reported on Google Code with ID 1671

OS version: Win7 Pro SP1 x64
ConEmu version: 140811 alpha 64-bit
Far version : Not using

*Bug description*
TCC/LE 13.06.77 64-bit console will not start.  
TCC/LE 13.06.77 32-bit console starts with no problem.

*Steps to reproduction*
I have both the 32-bit and 64-bit version of TCC/LE version 13.06.77 installed on my
machine.  I'm running the 64-bit version of ConEmu and I cannot start the 64-bit version
of TCC/LE in a console window.  I always get the following error : ConEmuC: Root process
was alive less than 10 sec, ExitCode=2.
The 32-bit version of the command shell works perfectly.
Not a HUGE deal since I can just run the 32-bit shell in ConEmu...just thought I would
document the issue.

Reported by decarlo.cliff on 2014-08-12 13:25:49

[Maximus5]

The same both run perfectly on my PC.

So I believe it is your PC configuration problem.
Most probably clink related.

Reported by ConEmu.Maximus5 on 2014-08-12 14:19:35

[Maximus5]

I do not have clink installed.

Reported by decarlo.cliff on 2014-08-12 14:44:49

[Maximus5]

Unimportant.
Try in outside of ConEmu. 
Try to run cmd as shell  and run tcc 64 from prompt.
Try ProcessMonitor to find what exactly is tcc64 doing to determine the cause of your
error.

Reported by ConEmu.Maximus5 on 2014-08-12 14:52:28

[Maximus5]

Running the x64 version of TCC/LE from a regular command prompt outside of ConEmu works
fine.  Trying to run the x64 version of TCC/LE from a command prompt (cmd) inside ConEmu
simply exits with no error message.  I have looked at the output from ProcessMonitor
and I really don't see anything that would indicate why it doesn't start.  The events
in ProcMon look pretty much the same for a launch from within a CMD prompt outside
ConEmu and from a CMD prompt inside ConEmu.  The process simply exits in the case where
it is running inside ConEmu.  I am attaching two output files from the ProcMon capture
(one from a launch inside ConEmu that didn't work and one from a CMD launch outside
ConEmu that did work)...maybe you will see something that I'm missing?

Reported by decarlo.cliff on 2014-08-12 15:09:09

---

- _Attachment: [NonWorkingLaunchTCCInsideConEMU.PML](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-4/NonWorkingLaunchTCCInsideConEMU.PML)_ - _Attachment: [WorkingLaunchTCCOutsideConEMU.PML](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-4/WorkingLaunchTCCOutsideConEMU.PML)_

[Maximus5]

This may be a conflict with your Bitdefender antivirus.
Try to disable it or add tcc to its exclusion list. 

Reported by ConEmu.Maximus5 on 2014-08-12 15:39:39

[Maximus5]

Issue 1316 
tcc was excited with code 2 too

Reported by ConEmu.Maximus5 on 2014-08-12 15:41:36

[Maximus5]

Yeah...I saw that post as well. That issue seemed to be fixed by uninstalling clink.
 I don't have clink installed...so I don't think it's the same issue.

Reported by decarlo.cliff on 2014-08-12 16:03:33

[Maximus5]

The idea is some third party program interfere normal tcc startup. That was clink in
the mentioned issue.
Because I have no sources of tcc ) I can't find the real issue. I believe JPSoft can
but not sure if they wish.

Reported by ConEmu.Maximus5 on 2014-08-12 16:09:52

[Maximus5]

Yeah..I'm sure they won't be interested in trying to diagnose...especially since TCC/LE
works perfectly fine *except* within ConEmu.  So I'm sure they will point the finger
back at ConEmu being the problem.

Reported by decarlo.cliff on 2014-08-13 18:21:41

[Maximus5]

Found this .gpf file that TCC/LE created...looks like it's an access violation.  Seems
to be related to tcc.exe and ConEmuHk64.dll not playing nice...

Reported by decarlo.cliff on 2014-08-13 18:56:34

---

- _Attachment: [TCMD.gpf](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-10/TCMD.gpf)_

[Maximus5]

OK, do the following.
1. Run cmd prompt
2. set ConEmuReportExe=tcc.exe
3. run 64-bit tcc, you will get the following message
---------------------------
tcc.exe loaded!
---------------------------
4. Do not press OK, goto ConEmu, right-click the tab, select Debug -> Debug active
process.
5. New tab must appears with many lines ) The last one must be
ConEmuC: Press Ctrl+Break to create minidump of debugging process
6. Not go to message box and press "OK" button.

I'm supposing tcc will crash and ConEmuC (debugger) will show suggestion to create
memory dump. Create full MemoryDump, zip it and upload it to DropBox or smth. Also,
I'm interested in the debugger log (output). Go to debugger tab and choose from tab
menu (right-click) Edit -> Copy all.

Reported by ConEmu.Maximus5 on 2014-08-13 20:12:24

[Maximus5]

FYI...just for kicks I tried this in Windows Safe mode and it worked fine.

I followed your steps to create the dump files...

Here is the debugger output...I will get the dumps uploaded tomorrow.

Reported by decarlo.cliff on 2014-08-13 21:56:14

---

- _Attachment: [coneum-debugger.txt](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-12/coneum-debugger.txt)_

[Maximus5]

I want to see that log after exception appears but not immediately after debugger attached.

Reported by ConEmu.Maximus5 on 2014-08-14 08:57:56

[Maximus5]

I've tried to copy/paste the debugger window after the tcc process crashes...but I cannot.
 It seems to be in an infinite crash cycle.  After creating the full dump, the crash
dialog comes back up immediately.  I've hit cancel a hundred times and it simply keeps
coming up...since that's a modal dialog I cannot access the underlying ConEmu window
at all.  I'm attaching a screenshot of the console...maybe that will help.  Also here
is the link to the full dump.

https://www.dropbox.com/s/66vhmklwjntk3fj/ConEmu-tcc64-fulldump.zip

Reported by decarlo.cliff on 2014-08-14 13:26:07

---

- _Attachment: [ConEmuCrash-ScreenShot.jpg](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-14/ConEmuCrash-ScreenShot.jpg)_

[Maximus5]

FYI.  The latest version 141029 alpha now allows the 64-bit TCC/LE console to start
without crashing...however it is not behaving properly.  When I issue a DOS command
like DIR for example I get no files listed...or if it is a directory with a lot of
files I get the occasional file listed with a lot of blank lines in between the files....very
strange.  Screenshot is attached.

Reported by decarlo.cliff on 2014-10-31 13:26:27

---

- _Attachment: [TCC-LE-64-Blank-Dir-Command.jpg](https://storage.googleapis.com/google-code-attachments/conemu-maximus5/issue-1671/comment-15/TCC-LE-64-Blank-Dir-Command.jpg)_

[Maximus5]

I can't believe it is ConEmu's related problem.
Tcc/le runs perfectly on my test PCs.

Create mini MemoryDump of this tcc instance.

Also, try this start command:
ConEmu -basic -cmd tcc

At last check your tcc config, may be there are some bad settings.

Reported by ConEmu.Maximus5 on 2014-10-31 15:16:01

[Maximus5]

You are correct.  I tried issuing several dir commands from my TCC/LE x64 outside of
ConEmu and it was doing the same strange thing with eventually returning blank results
for the directory listing.  Anyway, I checked and I had at one point started playing
around with the compatibility settings and had left it set to compatibility for Windows
7 (which is what I'm running anyway...so no need for that!)  If I uncheck the compatibility
setting it starts working properly.  So now with the latest build of ConEmu my TCC/LE
x64 version is now working perfectly within ConEmu!!!  Thank you!

Reported by decarlo.cliff on 2014-10-31 16:23:38

[Maximus5]

Reported by ConEmu.Maximus5 on 2014-10-31 16:48:18

• Status changed: Done
• Labels added: tcc