WIP: Add examples for Start-DebugAttachSession

[jborean93]

PR Summary

Adds examples to demonstrate how the new Start-DebugAttachSession function added in PowerShell Editor Services can be used.

The new function is attached by the PR PowerShell/PowerShellEditorServices#2249.

PR Checklist

Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets.
Please mark anything not applicable to this PR NA.

• PR has a meaningful title
• Summarized changes
• [NA] PR has tests
• This PR is ready to merge and is not work in progress
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

[Copilot]

Pull Request Overview

This PR adds example scripts demonstrating the usage of the new Start-DebugAttachSession function from PowerShell Editor Services. The examples show how to attach a debugger to a child PowerShell process using custom named pipes.

• Provides a target script that can be debugged when launched as a child process
• Demonstrates the complete workflow for attaching to and debugging external PowerShell processes
• Includes handling for both Windows PowerShell 5.1 and PowerShell Core compatibility

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
examples/ChildDebugSessionTarget.ps1	Target script that runs in a child process and waits for debugger attachment
examples/ChildDebugSessionAttach.ps1	Main example script showing how to launch and attach to a child PowerShell process

[Copilot]

Hardcoding 'pwsh' assumes PowerShell Core is available. Consider using $PSVersionTable.PSEdition to detect the current PowerShell edition and use 'powershell' for Windows PowerShell or 'pwsh' for PowerShell Core, or provide a parameter to specify the executable.

Suggested change

	$procParams = @{
	FilePath = 'pwsh'
	$psExecutable = if ($PSVersionTable.PSEdition -eq 'Core') { 'pwsh' } else { 'powershell' }
	$procParams = @{
	FilePath = $psExecutable

[Copilot]

The polling loop calls Get-Runspace repeatedly without any delay optimization. Consider adding a small delay before each check or implementing exponential backoff to reduce unnecessary CPU usage during the wait period.

Suggested change

	while ($true) {
	if (Get-Runspace | Where-Object { $_.Id -notin $runspaces.Id }) {
	break
	}
	Start-Sleep -Seconds 1
	$currentDelay = 1 # Initial delay duration in seconds
	$maxDelay = 16 # Maximum delay duration in seconds
	while ($true) {
	if (Get-Runspace | Where-Object { $_.Id -notin $runspaces.Id }) {
	break
	}
	Start-Sleep -Seconds $currentDelay
	$currentDelay = [math]::Min($currentDelay * 2, $maxDelay) # Exponential backoff

[Copilot]

The infinite loop lacks a timeout mechanism. Consider adding a maximum wait time to prevent the script from hanging indefinitely if the debugger never attaches.

Suggested change

	$runspaces = Get-Runspace
	while ($true) {
	if (Get-Runspace | Where-Object { $_.Id -notin $runspaces.Id }) {
	break
	}
	Start-Sleep -Seconds 1
	$runspaces = Get-Runspace
	$maxWaitTime = 60 # Maximum wait time in seconds
	$elapsedTime = 0 # Initialize elapsed time
	while ($true) {
	if (Get-Runspace | Where-Object { $_.Id -notin $runspaces.Id }) {
	break
	}
	Start-Sleep -Seconds 1
	$elapsedTime += 1
	if ($elapsedTime -ge $maxWaitTime) {
	Write-Host "Timeout reached while waiting for debugger to attach."
	break
	}