Syntax error with WinDBG command line -c ".cls;g"
in [Device Drivers]
|
Prev: Repost: Signed catalog file giving me "can't verify publisher" err
Next: DTM failed "Verify WDF Coinstaller Version for KMDF"
From: Satya on 23 Sep 2010 15:16 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" <Satya(a)discussions.microsoft.com> wrote in message > news:D4C208E0-053A-45A9-87AB-269141485774(a)microsoft.com... > > 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 > >> . > >>
From: Scott Noone on 27 Sep 2010 12:24
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" <Satya(a)discussions.microsoft.com> wrote in message news:847199AB-CE7D-475C-BE36-37CE0B2378E2(a)microsoft.com... > 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" <Satya(a)discussions.microsoft.com> wrote in message >> news:D4C208E0-053A-45A9-87AB-269141485774(a)microsoft.com... >> > 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 >> >> . >> >> |