Problems with Windbg command line and workspaces

WINDBG
1

Hi,
With the latests versions of Windbg whenever I use the following command
line WinDbg fails to get into debugging mode:

“c:\program files\debugging tools for windows\windbg” -k 1394:channel=
60,symlink=instance -c SQE:BL -W workspacename

However when I remove the “-W workspacename” parameter it starts just fine.

Can you confirm that this is a bug in WinDbg? Can it get fixed in the
next release…

2

Your command line as posted isn’t valid; do you get a popup to that
effect?
I removed a space after channel= and quoted the command string (changing
colon to semicolon) and think this might work better for you:

“c:\program files\debugging tools for windows\windbg” -k
1394:channel=60,symlink=instance -c “SQE;BL” -W workspacename

Thanks,
Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Cariddi
Sent: Friday, September 09, 2005 5:43 AM
To: Kernel Debugging Interest List
Subject: [windbg] Problems with Windbg command line and workspaces

Hi,
With the latests versions of Windbg whenever I use the following
command
line WinDbg fails to get into debugging mode:

“c:\program files\debugging tools for windows\windbg” -k 1394:channel=
60,symlink=instance -c SQE:BL -W workspacename

However when I remove the “-W workspacename” parameter it starts just
fine.

Can you confirm that this is a bug in WinDbg? Can it get fixed in the
next release…

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com