Done Can support be added to run TPipe from BDebugger?

[MGibs]

A .btm file containing a TPipe command cannot successfully execute TPipe from within BDebugger, making debugging anything after the TPipe command problematic.

This is still not able to be done in Version 36.

Is it possible to make this work in a future version?

See thread here for additional details.

 

[rconn]

I am not aware of any problems running the TPIPE command in BDEBUGGER (other than the expected behavior when you're piping to TPIPE in another TCC session).

Can you provide a simplified example of what you want to do and how it's failing?

 

[Joe Caverly]

I was able to duplicate the issue.

I tried the example @MGibs provided in the link in the OP, and received

TCC: (Sys) R:\TestTPipe.btm [2]  The parameter is incorrect.
 "Error - Can't access TextPipeEngine64.dll"

E:\Utils>ver

TCC  36.00.17 x64   Windows 10 [Version 10.0.19045.7058]

Joe

 

[MGibs]

I am not aware of any problems running the TPIPE command in BDEBUGGER (other than the expected behavior when you're piping to TPIPE in another TCC session).

Can you provide a simplified example of what you want to do and how it's failing?

@echo off
if exist "E:\TestDir\z_Logfile_UPPER.txt" del "E:\TestDir\z_Logfile_UPPER.txt"

tpipe /input="E:\TestDir\z_Logfile.txt" /output="E:\TestDir\z_Logfile_UPPER.txt" /simple=5

quit

 

[rconn]

I have patched this for v36.0.18.

Turned out to not be related to TCC, BDEBUGGER, TPIPE, or TextPipeEngine64.dll. The RTL was trying to attach CBT hooks to the TextPipeEngine64 hidden COM windows (even though I had expressly told the RTL not to do that). The hooking didn't go well and threw an exception, which TPIPE caught but didn't know what had caused it. So TPIPE printed a generic system error message and exited.