| external help file | Microsoft.PowerShell.Commands.Utility.dll-Help.xml | |
|---|---|---|
| Locale | en-US | |
| Module Name | Microsoft.PowerShell.Utility | |
| ms.date | 01/20/2023 | |
| online version | https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/get-psbreakpoint?view=powershell-7.6&WT.mc_id=ps-gethelp | |
| schema | 2.0.0 | |
| aliases |
|
|
| title | Get-PSBreakpoint |
Gets the breakpoints that are set in the current session.
Get-PSBreakpoint [[-Script] <String[]>] [-Runspace <Runspace>] [<CommonParameters>]
Get-PSBreakpoint [[-Script] <String[]>] -Command <String[]> [-Runspace <Runspace>] [<CommonParameters>]
Get-PSBreakpoint [[-Script] <String[]>] -Variable <String[]> [-Runspace <Runspace>] [<CommonParameters>]
Get-PSBreakpoint [[-Script] <String[]>] [-Type] <BreakpointType[]> [-Runspace <Runspace>] [<CommonParameters>]
Get-PSBreakpoint [-Id] <Int32[]> [-Runspace <Runspace>] [<CommonParameters>]
The Get-PSBreakpoint cmdlet gets the breakpoints that are set in the current session. You can use
the cmdlet parameters to get particular breakpoints.
A breakpoint is a point in a command or script where execution stops temporarily so that you can
examine the instructions. Get-PSBreakpoint is one of several cmdlets designed for debugging
PowerShell scripts and commands. For more information about the PowerShell debugger, see
about_Debuggers.
This command gets all breakpoints set on all scripts and functions in the current session.
Get-PSBreakpointThis command gets the breakpoint with breakpoint ID 2.
Get-PSBreakpoint -Id 2Function :
IncrementAction :
Enabled :
TrueHitCount : 0
Id : 2
Script : C:\ps-test\sample.ps1
ScriptName : C:\ps-test\sample.ps1
These commands show how to get a breakpoint by piping a breakpoint ID to Get-PSBreakpoint.
$B = `Set-PSBreakpoint` -Script "sample.ps1" -Command "Increment"
$B.Id | Get-PSBreakpointThe Set-PSBreakpoint cmdlet creates a breakpoint on the Increment function in the Sample.ps1
script and saves the breakpoint object in the $B variable. The Id property of the breakpoint
object in the $B variable is piped to the Get-PSBreakpoint cmdlet to display the breakpoint
information.
This command gets all of the breakpoints in the Sample.ps1 and SupportScript.ps1 files.
Get-PSBreakpoint -Script "Sample.ps1, SupportScript.ps1"This command does not get other breakpoints that might be set in other scripts or on functions in the session.
This command gets all Command breakpoints that are set on Read-Host or Write-Host commands in
the Sample.ps1 file.
Get-PSBreakpoint -Command "Read-Host, Write-Host" -Script "Sample.ps1"Get-PSBreakpoint -Type Command -Script "Sample.ps1"This command gets all Command breakpoints in the Sample.ps1 file.
This command gets breakpoints that are set on the $Index and $Swap variables in the current
session.
Get-PSBreakpoint -Variable "Index, Swap"This command gets all line and variable breakpoints in the Sample.ps1 script.
Get-PSBreakpoint -Type Line, Variable -Script "Sample.ps1"In this example, a job is started and a breakpoint is set to break when the Set-PSBreakpoint is
run. The runspace is stored in a variable and passed to the Get-PSBreakpoint command with the
Runspace parameter. You can then inspect the breakpoint in the $breakpoint variable.
Start-Job -ScriptBlock {
Set-PSBreakpoint -Command Start-Sleep
Start-Sleep -Seconds 10
}
$runspace = Get-Runspace -Id 1
$breakpoint = Get-PSBreakpoint -Runspace $runspaceSpecifies an array of command breakpoints that are set on the specified command names. Enter the command names, such as the name of a cmdlet or function.
Type: System.String[]
Parameter Sets: Command
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseSpecifies the breakpoint IDs that this cmdlet gets. Enter the IDs in a comma-separated list. You can
also pipe breakpoint IDs to Get-PSBreakpoint.
Type: System.Int32[]
Parameter Sets: Id
Aliases:
Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseSpecifies the Id of a Runspace object so you can interact with breakpoints in the specified runspace.
This parameter was added in PowerShell 7.2.
Type: Runspace
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseSpecifies an array of scripts that contain the breakpoints. Enter the path (optional) and names of one or more script files. If you omit the path, the default location is the current directory.
Type: System.String[]
Parameter Sets: Script, Variable, Command, Type
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseSpecifies an array of breakpoint types that this cmdlet gets. Enter one or more types. The acceptable values for this parameter are:
- Line
- Command
- Variable
You can also pipe breakpoint types to Get-PSBreakpoint.
Type: Microsoft.PowerShell.Commands.BreakpointType[]
Parameter Sets: Type
Aliases:
Accepted values: Line, Variable, Command
Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseSpecifies an array of variable breakpoints that are set on the specified variable names. Enter the variable names without dollar signs.
Type: System.String[]
Parameter Sets: Variable
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
You can pipe breakpoint IDs to this cmdlet.
You can pipe breakpoint types to this cmdlet.
This cmdlet returns objects that represent the breakpoints in the session.
PowerShell includes the following aliases for Get-PSBreakpoint:
- All platforms:
gbp