Excuting ActiveState perl from powershell script makes debugger hang.
Hi,
I have a Powershell script which - among other things - executes a perl script. This has worked fine, but now the debugger never returns from the execution of perl. Killing the perl process makes the debugger work fine again. The Powershell script runs fine both manually and under scheduler.
It’s been a while since I have debugged the script, so I don’t know when it stopped working.
This code snippet triggers the problem:
#######################################
"start"
$cmd = { perl.exe -v }
invoke-command $cmd ← hang
"over and out"
#######################################
As can be seen, even a very simple perl command triggers the problem. It’s not related to a perl script.
I have tried different ways to spawn perl - all with same result.
Perl version is “perl 5, version 24, subversion 3 (v5.24.3) built for MSWin32-x64-multi-thread”
Which is a bit old, but the newest still using “ppm” for maintenance of modules.
I have tried to enable diagnostic logging, but that seems not work. At least nothing is written to log.txt.
I have no idea whether PoshTools is making the problem - but I would really appreciate some help to move on in troubleshooting.
Best regards
Poul
Powershell Tools:
5.1.1
$PSVersionTable
Name Value
PSVersion 5.1.18362.145
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.145
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Visual Studio:
Microsoft Visual Studio Community 2019
Version 16.3.9
VisualStudio.16.Release/16.3.9+29509.3
Microsoft .NET Framework
Version 4.8.03752
