Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Unlike `Start-Job`, `Start-ThreadJob` doesn't respect a `Set-PSBreakpoint -Command` call in connection with `Debug-Job`

Aberta
  • Algo errado?
#39 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
powershell
Domínio
backend

Direção de pesquisa

Start with the Start-ThreadJob reproduction and compare its breakpoint behavior with Start-Job and ForEach-Object -AsJob -Parallel. Read the thread job debugging and job state handling entry points, then trace why the breakpoint does not keep the thread job running for Debug-Job. Done means the reproduction enters the debugger at foo as expected.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.
Steps to reproduce

  • When using Set-PSBreakpoint -Command from a background (child process-based) job, the Set-PSBreakpoint -Command is honored (assuming that the job is already in the Running state - see https://github.com/PowerShell/PowerShell/issues/21258): the breakpoint suspends execution until the Debug-Job call connects.

  • By contrast, with a thread job, that doesn't work: the thread job runs to completion, irrespective of the break point; the same applies to ForEach-Object -AsJob -Parallel.

Write-Verbose -Verbose 'Creating a job that uses `Set-PSBreakpoint -Command foo`'
# NOTE: If you substitute `Start-Job` on the next line, the behavior is as expected.
$job = Start-ThreadJob {

  function foo {
    'hi'
  }
  
  Set-PSBreakpoint -Command foo

  foo

} 

Write-Verbose -Verbose 'Waiting an arbitrary amount of time (e.g., 3 seconds)...'
Start-Sleep 3

Write-Verbose -Verbose 'Initiating debugging...'
$job | Debug-Job

# Clean up.
$job | Remove-Job -Force
Expected behavior
Hit Command breakpoint on 'foo'

At line:3 char:16
+   function foo {
+

That is, the break point should be honored, irrespective of when Debug-Job is invoked,
and the debugger should be entered.

This is indeed how it works with a Start-Job (child process-based) job.

Actual behavior
Debug-Job: /path/to/some.ps1:42
Line |
  19 |  $job | Debug-Job
     |         ~~~~~~~~~
     | The provided job and all child jobs were examined but no jobs were found that could be debugged.  In order to debug a job or child job the job must support debugging and
     | also be in a running state.

That is, the thread job ran to completion without honoring the break point, and the attempt to call Debug-Job came too late.

Error details

No response

Environment data
PowerShell 7.5.0-preview.3
Version

2.0.3, as shipped with PowerShell Core v7.5.0-preview.3

Visuals

No response

Linguagem predominante
PowerShell
Estrelas
37
Forks
22
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PowerShell/ThreadJob

Todas as issues de PowerShell/ThreadJob

Issues semelhantes

Mais issues de Backend & API Design

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.