Vista - set-psdebug -trace 0

User Guide :

The set-psdebug -trace 0 command disables any tracing and stepping.

still (after set-psdebug -trace 2 ) :

MowPS>Set-PSDebug -trace 0
DEBUG: 1+ Set-PSDebug -trace 0
MowPS>2145806576 -2145462512
DEBUG: 1+ 2145806576 -2145462512
344064

MowPS>Set-PSDebug -off
DEBUG: 1+ Set-PSDebug -off
MowPS>2145806576 -2145462512
344064
MowPS>2145806576 -2145462512

MowPS>set-psdebug -?

....
....
PARAMETERS
-Trace <System.Int32>
This parameter sets the trace level as follows:
0 - turn script tracing off
1 - trace script lines as they are executed
2 - as well as script lines, also trace variable assignments,
function calls and scripts.
....
....

I think this is correct but confusing

if I use -trace 1 I can turn it of by -trace 0
but if I use -trace 2 I need -Off to turn it of.

hmm but then again, nope also not right :

MowPS>set-psdebug -Trace 1
MowPS>2145806576 -2145462512
DEBUG: 1+ 2145806576 -2145462512
344064
MowPS>Set-PSDebug -trace 0
DEBUG: 1+ Set-PSDebug -trace 0
MowPS>2145806576 -2145462512
DEBUG: 1+ 2145806576 -2145462512
344064

gr /\/\o\/\/

this is a bug (which we're fixing)

jim

--
James W. Truher [MSFT]
Windows PowerShell Program Management
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

"/\/\o\/\/" <no@spam.mow> wrote in message
news:O0RbkJ1gGHA.4712@TK2MSFTNGP05.phx.gbl...
> User Guide :
>
> The set-psdebug -trace 0 command disables any tracing and stepping.
>
> still (after set-psdebug -trace 2 ) :
>
> MowPS>Set-PSDebug -trace 0
> DEBUG: 1+ Set-PSDebug -trace 0
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
>
> MowPS>Set-PSDebug -off
> DEBUG: 1+ Set-PSDebug -off
> MowPS>2145806576 -2145462512
> 344064
> MowPS>2145806576 -2145462512
>
> MowPS>set-psdebug -?
>
> ...
> ...
> PARAMETERS
> -Trace <System.Int32>
> This parameter sets the trace level as follows:
> 0 - turn script tracing off
> 1 - trace script lines as they are executed
> 2 - as well as script lines, also trace variable assignments,
> function calls and scripts.
> ...
> ...
>
> I think this is correct but confusing
>
> if I use -trace 1 I can turn it of by -trace 0
> but if I use -trace 2 I need -Off to turn it of.
>
> hmm but then again, nope also not right :
>
> MowPS>set-psdebug -Trace 1
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
> MowPS>Set-PSDebug -trace 0
> DEBUG: 1+ Set-PSDebug -trace 0
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
>
> gr /\/\o\/\/

It's a known bug has been fixed.

-bruce

--
Bruce Payette [MSFT]
Windows PowerShell Technical Lead
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.



"/\/\o\/\/" <no@spam.mow> wrote in message
news:O0RbkJ1gGHA.4712@TK2MSFTNGP05.phx.gbl...
> User Guide :
>
> The set-psdebug -trace 0 command disables any tracing and stepping.
>
> still (after set-psdebug -trace 2 ) :
>
> MowPS>Set-PSDebug -trace 0
> DEBUG: 1+ Set-PSDebug -trace 0
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
>
> MowPS>Set-PSDebug -off
> DEBUG: 1+ Set-PSDebug -off
> MowPS>2145806576 -2145462512
> 344064
> MowPS>2145806576 -2145462512
>
> MowPS>set-psdebug -?
>
> ...
> ...
> PARAMETERS
> -Trace <System.Int32>
> This parameter sets the trace level as follows:
> 0 - turn script tracing off
> 1 - trace script lines as they are executed
> 2 - as well as script lines, also trace variable assignments,
> function calls and scripts.
> ...
> ...
>
> I think this is correct but confusing
>
> if I use -trace 1 I can turn it of by -trace 0
> but if I use -trace 2 I need -Off to turn it of.
>
> hmm but then again, nope also not right :
>
> MowPS>set-psdebug -Trace 1
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
> MowPS>Set-PSDebug -trace 0
> DEBUG: 1+ Set-PSDebug -trace 0
> MowPS>2145806576 -2145462512
> DEBUG: 1+ 2145806576 -2145462512
> 344064
>
> gr /\/\o\/\/