Populate Runspace & Debugger properties

[TylerLeonhardt]

I noticed that Start-Job returns an object that has a property that allows you to get the runspace:

$myJob = Start-Job -ScriptBlock { gci }
$myJob.ChildJobs[0].Runspace
 Id Name            ComputerName    Type          State         Availability
 -- ----            ------------    ----          -----         ------------
  3 Runspace3       localhost       Remote        Closed        None

It can also get the debugger:

$myJob.ChildJobs[0].Debugger

InBreakpoint DebugMode IsActive InstanceId
------------ --------- -------- ----------
       False   Default    False 00000000-0000-0000-0000-000000000000

However, the ThreadJob that comes back from Start-ThreadJob does have a Debugger property but it's not set:

$myThreadJob = Start-ThreadJob -ScriptBlock { gci }
$myThreadJob.Debugger

Can we populate that and also a Runspace property? I think that'll help with debugging threadjobs.

[Luiz-Monad]

So that's why debugging doesn't seem to work

[Luiz-Monad]

Nevermind, this project is obsolete, they really should upgrade the README. I migrated to 'Microsoft.PowerShell.ThreadJob' https://github.com/Powershell/ThreadJob. As it is now being maintained by the Powershell team itself ( PowerShell/PowerShell#19744 ).

It works now, you just have to attach to the Powershell instance you want to debug, then you can run [System.Management.Automation.Runspaces.Runspace]::DefaultRunspace from the Thread you started before doing a Wait-Debugger, then you get that information.