Partager via

Debugging Monad Scripts, Part 4: set-mshdebug

  • Article

Did your command or script fail and/or report an error?  We hope to have a proper script debugger in a future version, but until then, MSH has some handy features to help you figure out what went wrong.  In this series of blog entries, I will present some of those features.  Thanks to Jim Truher [MSFT], Bruce Payette [MSFT], and Jeff Jones [MSFT] for their help in putting this together.

See the Windows "Monad" Shell Beta 2 Documentation Pack (https://www.microsoft.com/downloads/details.aspx?FamilyID=8a3c71d1-18e5-49d7-952a-c55d694ecee3&displaylang=en) for general information about Monad.

Part 1: https://blogs.msdn.com/monad/archive/2005/11/04/489138.aspx (Terminating vs. Non-Terminating Errors, ErrorRecord)
Part 2: https://blogs.msdn.com/monad/archive/2005/11/08/490130.aspx ($error)
Part 3: https://blogs.msdn.com/monad/archive/2005/11/09/490625.aspx (write-host)

Jon Newman [MSFT]

 

set-mshdebug [-Trace 0..2] [-Step] [-Off]

If your error is reproducible, you can turn on script tracing, or even get MSH to suspend and restart your script so that you can interactively look at the shell variables and the state of the world in the middle of your script. Look at this transcript:

MSH C:\temp> get-content .\test.msh
$a = "line1"
$a
$a = "line2"
$a
MSH C:\temp> .\test.msh
line1
line2
MSH C:\temp> set-mshdebug -trace 2
MSH C:\temp> .\test.msh
DEBUG: 1+ .\test.msh
DEBUG: ! CALL script 'test.msh'
DEBUG: 1+ $a = "line1"
DEBUG: ! SET $a = 'line1'.
DEBUG: 2+ $a
line1
DEBUG: 3+ $a = "line2"
DEBUG: ! SET $a = 'line2'.
DEBUG: 4+ $a
line2
MSH C:\temp>

"set-mshdebug -trace 2" turns on script tracing: level 0 is off, level 1 is line-by-line tracing, and level 2 also traces variable assignments, function calls, script invocation, and trap dispatches.

"set-mshdebug -Step" lets you step through your script one line at a time, almost as if it were in the debugger. You can use "No" or "No to All" to halt the script, or "Suspend" to suspend its operation temporarily. Notice how the prompt changes from ">" to ">>>". While the script is suspended, you can check the values of shell variables, or run entirely new commands or scripts, then return to the suspended script with "exit".

MSH C:\temp> set-mshdebug -Step
MSH C:\temp> .\test.msh
Continue with this operation?
1+ .\test.msh
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 1+ .\test.msh
Continue with this operation?
1+ $a = "line1"
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 1+ $a = "line1"
Continue with this operation?
2+ $a
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): suspend
MSH C:\temp>>> $a
line1
MSH C:\temp>>> exit
Continue with this operation?
2+ $a
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 2+ $a
line1
Continue with this operation?
3+ $a = "line2"
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): h
WriteDebug stopped because the DebugPreference was 'Stop'.
At line:1 char:1
+ . <<<< \test.msh
MSH C:\temp>

Note that formatting scripts will also get the step-step treatment. You're most likely to see this when you get a non-terminating error:

MSH C:\temp> set-mshdebug -step
MSH C:\temp> get-content c:\nosuchfile
Continue with this operation?
1+ get-content c:\nosuchfile
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 1+ get-content c:\nosuchfile
Continue with this operation?
2+ if ($ErrorView -ne "CategoryView") {
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 2+ if ($ErrorView -ne "CategoryView") {
Continue with this operation?
3+ $myinv = $_.InvocationInfo
[Y] Yes [A] Yes to All [H] Halt [S] Suspend [?] Help (default is "Y"): y
DEBUG: 3+ $myinv = $_.InvocationInfo
...

Comments

  • Anonymous
    April 25, 2006

    Did your command or script fail and/or report an error?&amp;nbsp; We hope to have a proper script debugger...
  • Anonymous
    April 25, 2006

    Did your command or script fail and/or report an error?&amp;nbsp; We hope to have a proper script debugger...
  • Anonymous
    April 25, 2006

    Did your command or script fail and/or report an error?&amp;nbsp; We hope to have a proper script debugger...
  • Anonymous
    June 24, 2007
    So why do you care about debugging powershell scripts? Umm unless you have the superhuman ability to