How to get debug prints in WinDbg from Vista

I'm trying to debug my property page provider application on 32bit variant
of Vista Ultimate by using WinDbg with a serial connection to try and
capture the snapshots being sent by the "OutputDebugString" calls, but
nothing comes out to the command window! The same application works just
fine under Windows XP, Server 2003, and Windows 2000.

I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls only
to learn that the former returns a FALSE to the local variable receiving the
value when the breakpoint is hit on the latter call. What isn't clear is
why the debug connection is established and control is passed to the
debugger, yet "IsDebuggerPresent" returns a false and "OutputDebugString"
calls are not routed through the connection?

I've tried setting the "Debug Print File" as defined in
http://www.osronline.com/article.cfm?article=295, but to no avail. Is there
another trick to getting debug print statements out of Vista to WinDbg that
I'm missing?

Ivan
Sat Jun 02 14:01:07 CDT 2007

multipost.
follow up on microsoft.public.debugger

--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
news:utDwW8HpHHA.4516@TK2MSFTNGP05.phx.gbl...
> I'm trying to debug my property page provider application on 32bit variant
> of Vista Ultimate by using WinDbg with a serial connection to try and
> capture the snapshots being sent by the "OutputDebugString" calls, but
> nothing comes out to the command window! The same application works just
> fine under Windows XP, Server 2003, and Windows 2000.
>
> I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls only
> to learn that the former returns a FALSE to the local variable receiving
> the
> value when the breakpoint is hit on the latter call. What isn't clear is
> why the debug connection is established and control is passed to the
> debugger, yet "IsDebuggerPresent" returns a false and "OutputDebugString"
> calls are not routed through the connection?
>
> I've tried setting the "Debug Print File" as defined in
> http://www.osronline.com/article.cfm?article=295, but to no avail. Is
> there
> another trick to getting debug print statements out of Vista to WinDbg
> that
> I'm missing?
>
>

Del
Tue Jun 05 14:52:54 CDT 2007

Well, since my roaming profile on Windows 2000 got scrogged and I had to
restore everything, it seems as though the indicated newsgroup does not even
appear to be available to subscribe to anymore!

So I am I to assume that the response given here means receiving the chance
of getting any response is slim and none? Small wonder Vista is getting
such a bad rap by those who really have to use and provide IHV support for
it!

I suppose I tell our sales and marketing that Vista drivers will be awhile
why we try to figure out all the things that were working just fine but were
changed because someone had a better idea, some of which were undocumented.

"Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
news:e7wOhhUpHHA.596@TK2MSFTNGP06.phx.gbl...
> multipost.
> follow up on microsoft.public.debugger
>
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
>
> "Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
> news:utDwW8HpHHA.4516@TK2MSFTNGP05.phx.gbl...
> > I'm trying to debug my property page provider application on 32bit
variant
> > of Vista Ultimate by using WinDbg with a serial connection to try and
> > capture the snapshots being sent by the "OutputDebugString" calls, but
> > nothing comes out to the command window! The same application works
just
> > fine under Windows XP, Server 2003, and Windows 2000.
> >
> > I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls
only
> > to learn that the former returns a FALSE to the local variable receiving
> > the
> > value when the breakpoint is hit on the latter call. What isn't clear
is
> > why the debug connection is established and control is passed to the
> > debugger, yet "IsDebuggerPresent" returns a false and
"OutputDebugString"
> > calls are not routed through the connection?
> >
> > I've tried setting the "Debug Print File" as defined in
> > http://www.osronline.com/article.cfm?article=295, but to no avail. Is
> > there
> > another trick to getting debug print statements out of Vista to WinDbg
> > that
> > I'm missing?
> >
> >
>
>

Del
Tue Jun 05 14:55:59 CDT 2007

I also find that even the google access does not recognize the indicated
newsgroup.

"Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
news:e7wOhhUpHHA.596@TK2MSFTNGP06.phx.gbl...
> multipost.
> follow up on microsoft.public.debugger
>
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
>
> "Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
> news:utDwW8HpHHA.4516@TK2MSFTNGP05.phx.gbl...
> > I'm trying to debug my property page provider application on 32bit
variant
> > of Vista Ultimate by using WinDbg with a serial connection to try and
> > capture the snapshots being sent by the "OutputDebugString" calls, but
> > nothing comes out to the command window! The same application works
just
> > fine under Windows XP, Server 2003, and Windows 2000.
> >
> > I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls
only
> > to learn that the former returns a FALSE to the local variable receiving
> > the
> > value when the breakpoint is hit on the latter call. What isn't clear
is
> > why the debug connection is established and control is passed to the
> > debugger, yet "IsDebuggerPresent" returns a false and
"OutputDebugString"
> > calls are not routed through the connection?
> >
> > I've tried setting the "Debug Print File" as defined in
> > http://www.osronline.com/article.cfm?article=295, but to no avail. Is
> > there
> > another trick to getting debug print statements out of Vista to WinDbg
> > that
> > I'm missing?
> >
> >
>
>

Del
Tue Jun 05 15:22:01 CDT 2007

Am I to assume this is the microsoft.public.windbg newsgroup?

"Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
news:O1N4Ku6pHHA.3512@TK2MSFTNGP06.phx.gbl...
> I also find that even the google access does not recognize the indicated
> newsgroup.
>
> "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
> news:e7wOhhUpHHA.596@TK2MSFTNGP06.phx.gbl...
> > multipost.
> > follow up on microsoft.public.debugger
> >
> > --
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > Use of any included script samples are subject to the terms specified at
> > http://www.microsoft.com/info/cpyright.htm
> >
> >
> > "Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
> > news:utDwW8HpHHA.4516@TK2MSFTNGP05.phx.gbl...
> > > I'm trying to debug my property page provider application on 32bit
> variant
> > > of Vista Ultimate by using WinDbg with a serial connection to try and
> > > capture the snapshots being sent by the "OutputDebugString" calls, but
> > > nothing comes out to the command window! The same application works
> just
> > > fine under Windows XP, Server 2003, and Windows 2000.
> > >
> > > I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls
> only
> > > to learn that the former returns a FALSE to the local variable
receiving
> > > the
> > > value when the breakpoint is hit on the latter call. What isn't clear
> is
> > > why the debug connection is established and control is passed to the
> > > debugger, yet "IsDebuggerPresent" returns a false and
> "OutputDebugString"
> > > calls are not routed through the connection?
> > >
> > > I've tried setting the "Debug Print File" as defined in
> > > http://www.osronline.com/article.cfm?article=295, but to no avail. Is
> > > there
> > > another trick to getting debug print statements out of Vista to WinDbg
> > > that
> > > I'm missing?
> > >
> > >
> >
> >
>
>

Ivan
Wed Jun 06 12:19:50 CDT 2007

Yeap. It was a typo. Sorry about that.

--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
news:%23akHv86pHHA.4212@TK2MSFTNGP04.phx.gbl...
> Am I to assume this is the microsoft.public.windbg newsgroup?
>
> "Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
> news:O1N4Ku6pHHA.3512@TK2MSFTNGP06.phx.gbl...
>> I also find that even the google access does not recognize the indicated
>> newsgroup.
>>
>> "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
>> news:e7wOhhUpHHA.596@TK2MSFTNGP06.phx.gbl...
>> > multipost.
>> > follow up on microsoft.public.debugger
>> >
>> > --
>> > --
>> > This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> > Use of any included script samples are subject to the terms specified
>> > at
>> > http://www.microsoft.com/info/cpyright.htm
>> >
>> >
>> > "Del Fredricks" <del.fredricks@ms.discussions.com> wrote in message
>> > news:utDwW8HpHHA.4516@TK2MSFTNGP05.phx.gbl...
>> > > I'm trying to debug my property page provider application on 32bit
>> variant
>> > > of Vista Ultimate by using WinDbg with a serial connection to try and
>> > > capture the snapshots being sent by the "OutputDebugString" calls,
>> > > but
>> > > nothing comes out to the command window! The same application works
>> just
>> > > fine under Windows XP, Server 2003, and Windows 2000.
>> > >
>> > > I've inserted the "IsDebuggerPresent" and "DebugBreak" function calls
>> only
>> > > to learn that the former returns a FALSE to the local variable
> receiving
>> > > the
>> > > value when the breakpoint is hit on the latter call. What isn't
>> > > clear
>> is
>> > > why the debug connection is established and control is passed to the
>> > > debugger, yet "IsDebuggerPresent" returns a false and
>> "OutputDebugString"
>> > > calls are not routed through the connection?
>> > >
>> > > I've tried setting the "Debug Print File" as defined in
>> > > http://www.osronline.com/article.cfm?article=295, but to no avail.
>> > > Is
>> > > there
>> > > another trick to getting debug print statements out of Vista to
>> > > WinDbg
>> > > that
>> > > I'm missing?
>> > >
>> > >
>> >
>> >
>>
>>
>
>