RE: Syntax error with WinDBG command line -c ".cls;g"

You may have better luck creating a script file and executing the script file
with $< syntax.

Satya
http://www.winprogger.com

"Senthil" wrote:

> I am using WinDBG 6.12.2.663 to debug a target (VMWare ware guest)
> over COM pipe. I intend to pass a command line that clears the screen
> and continues debugging. So, I pass -c ".cls;g" and I get the syntax
> error
>
> Processing initial command '.cls;g'
> 0: kd> .cls;g
> ^ Syntax error in '.cls;g'
>
> It works fine if pass just -c ".cls"
>
> WinDBG help states that "If you are starting a debugging client, this
> command must be intended for the debugging server. Client-specific
> commands, such as .lsrcpath, are not allowed. ". Is that wha the issue
> is?
>
> I am not using client/server setup here, though I would agree that my
> debugger is running in client mode here for all practical purposes.
> Why is this restriction and is there a way for me to get .cls working
> with other commands via -c ""?
>
> Thanks,
> Senthil
> .
>

That's not going to work either, some commands can't be scripted and .cls is
one of them.

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
http://twitter.com/analyzev

"Satya" <> wrote in message
news4C208E0-053A-45A9-87AB-...
> You may have better luck creating a script file and executing the script
> file
> with $< syntax.
>
> Satya
> http://www.winprogger.com
>
> "Senthil" wrote:
>
>> I am using WinDBG 6.12.2.663 to debug a target (VMWare ware guest)
>> over COM pipe. I intend to pass a command line that clears the screen
>> and continues debugging. So, I pass -c ".cls;g" and I get the syntax
>> error
>>
>> Processing initial command '.cls;g'
>> 0: kd> .cls;g
>> ^ Syntax error in '.cls;g'
>>
>> It works fine if pass just -c ".cls"
>>
>> WinDBG help states that "If you are starting a debugging client, this
>> command must be intended for the debugging server. Client-specific
>> commands, such as .lsrcpath, are not allowed. ". Is that wha the issue
>> is?
>>
>> I am not using client/server setup here, though I would agree that my
>> debugger is running in client mode here for all practical purposes.
>> Why is this restriction and is there a way for me to get .cls working
>> with other commands via -c ""?
>>
>> Thanks,
>> Senthil
>> .
>>

"rogero" <> wrote in message
news:e86fb688-d365-42a2-b768-
> Anyone know why .cls is special? Other dot commands I try seem happy
> with the space:
>
> windbg -c " .asm ; dd eip l1 " cmd.exe

..cls is a WinDBG GUI command, not a debugger engine command. So, it's
stripped out by the GUI code and not passed along to DbgEng. The list of
other commands like this is here:

http://msdn.microsoft.com/en-us/libr...37(VS.85).aspx


-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
http://twitter.com/analyzev

"rogero" <> wrote in message
news:e86fb688-d365-42a2-b768-...
> On Sep 9, 1:25 pm, "Scott Noone" <sno...@osr.com> wrote:
>> If you do that the .cls will work but everything else on the line will be
>> ignored.
>>
>> -scott
>>
>> --
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources,
>> Inc.http://www.osronline.comhttp://twitter.com/analyzev
>>
>> "rogero" <roger....@gmail.com> wrote in message
>>
>> news:9d9ad3d4-6f16-4683-80e1-...
>>
>>
>>
>> > On Sep 8, 7:21 pm, Senthil <sanasent...@gmail.com> wrote:
>> >> Thank you for all your comments. But at this point nothing is working.
>> >> Scripting doesn't work either as suggested by Scott. Kind of
>> >> frustrating, but I guess I can live with it.
>> >> Senthil
>>
>> > Try a space before the semicolon.
>> > Strange but true...
>>
>> > Roger.- Hide quoted text -
>>
>> - Show quoted text -
>
> Anyone know why .cls is special? Other dot commands I try seem happy
> with the space:
>
> windbg -c " .asm ; dd eip l1 " cmd.exe
>
> roger.

I tried this and you are right. It seems this is a windbg issue. If you use
kd this works nicely. Here is what I tried in 6.12.2.633 x86 build of Windbg
package-

- created a script file that has 2 lines in it (mark that ; is adsent)
..cls
g
- in command prompt kd -k 1394:channel=1 -cf <script path>

Satya
Winprogger
http://www.winprogger.com

"Scott Noone" wrote:

> That's not going to work either, some commands can't be scripted and .cls is
> one of them.
>
> -scott
>
> --
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
> http://twitter.com/analyzev
>
> "Satya" <> wrote in message
> news4C208E0-053A-45A9-87AB-...
> > You may have better luck creating a script file and executing the script
> > file
> > with $< syntax.
> >
> > Satya
> > http://www.winprogger.com
> >
> > "Senthil" wrote:
> >
> >> I am using WinDBG 6.12.2.663 to debug a target (VMWare ware guest)
> >> over COM pipe. I intend to pass a command line that clears the screen
> >> and continues debugging. So, I pass -c ".cls;g" and I get the syntax
> >> error
> >>
> >> Processing initial command '.cls;g'
> >> 0: kd> .cls;g
> >> ^ Syntax error in '.cls;g'
> >>
> >> It works fine if pass just -c ".cls"
> >>
> >> WinDBG help states that "If you are starting a debugging client, this
> >> command must be intended for the debugging server. Client-specific
> >> commands, such as .lsrcpath, are not allowed. ". Is that wha the issue
> >> is?
> >>
> >> I am not using client/server setup here, though I would agree that my
> >> debugger is running in client mode here for all practical purposes.
> >> Why is this restriction and is there a way for me to get .cls working
> >> with other commands via -c ""?
> >>
> >> Thanks,
> >> Senthil
> >> .
> >>

I put up a couple of blog posts on the issue and a very, very hacky
workaround:

http://analyze-v.com/?p=716
http://analyze-v.com/?p=719

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com


"Satya" <> wrote in message
news:847199AB-CE7D-475C-BE36-...
> I tried this and you are right. It seems this is a windbg issue. If you
> use
> kd this works nicely. Here is what I tried in 6.12.2.633 x86 build of
> Windbg
> package-
>
> - created a script file that has 2 lines in it (mark that ; is adsent)
> .cls
> g
> - in command prompt kd -k 1394:channel=1 -cf <script path>
>
> Satya
> Winprogger
> http://www.winprogger.com
>
> "Scott Noone" wrote:
>
>> That's not going to work either, some commands can't be scripted and .cls
>> is
>> one of them.
>>
>> -scott
>>
>> --
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>> http://twitter.com/analyzev
>>
>> "Satya" <> wrote in message
>> news4C208E0-053A-45A9-87AB-...
>> > You may have better luck creating a script file and executing the
>> > script
>> > file
>> > with $< syntax.
>> >
>> > Satya
>> > http://www.winprogger.com
>> >
>> > "Senthil" wrote:
>> >
>> >> I am using WinDBG 6.12.2.663 to debug a target (VMWare ware guest)
>> >> over COM pipe. I intend to pass a command line that clears the screen
>> >> and continues debugging. So, I pass -c ".cls;g" and I get the syntax
>> >> error
>> >>
>> >> Processing initial command '.cls;g'
>> >> 0: kd> .cls;g
>> >> ^ Syntax error in '.cls;g'
>> >>
>> >> It works fine if pass just -c ".cls"
>> >>
>> >> WinDBG help states that "If you are starting a debugging client, this
>> >> command must be intended for the debugging server. Client-specific
>> >> commands, such as .lsrcpath, are not allowed. ". Is that wha the issue
>> >> is?
>> >>
>> >> I am not using client/server setup here, though I would agree that my
>> >> debugger is running in client mode here for all practical purposes.
>> >> Why is this restriction and is there a way for me to get .cls working
>> >> with other commands via -c ""?
>> >>
>> >> Thanks,
>> >> Senthil
>> >> .
>> >>