PR Summary

Fix #3260

PowerShell has a handler for Ctrl+Break, to break into debugger on the currently running script. This makes it possible to cause debugger to stop on the script that PSReadLine is running internally while it's idle (not processing any input keys). For example, it may be triggering the pulse pipeline for event processing by running the script "0", and Ctrl+Break causes the debugger to break in the script and pause the execution.

When this happens, a nested prompt will be provided to the user, which calls PSReadLine again to process input, which causes the re-entry of PSReadLine and make it crash.

The fix is to make the internal PSReadLine script hidden from PowerShell debugger, just like the built-in functions in PowerShell, such as prompt. Then Ctrl+Break won't cause debugger to interrupt the script execution in PSReadLine.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure you've added one or more new tests
• Make sure you've tested these changes in terminals that PowerShell is commonly used in (i.e. conhost.exe, Windows Terminal, Visual Studio Code Integrated Terminal, etc.)
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed at PowerShell-Docs
    • Doc Issue filed:

Microsoft Reviewers: Open in CodeFlow