This is Event Tracing For Windows nonsense that is not compatible with standard printf formatting. Some will claim this as a bonus feature for ETW, others as yet another reason to avoid ETW like the plague. DebugView shows you printf formatted output, not ETW output, and somewhat by accident printf format processing ends up outputting unknown format specifications as you observe.
To recap: the driver you are looking at can be compiled to output to the standard dbgprint console or to ETW (or perhaps both) and uses nonstandard ETW-only format specifications which result in the observed behavior in DebugView.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mattias Br?ndstr?m
Sent: Tuesday, October 30, 2007 8:55 AM
To: Windows System Software Devs Interest List
Subject: SV: [ntdev] DbgPrint, &!STATUS!
OK. I’m using DebugView and the only thing I get as output from this is !STATUS!. Is there some configuration that needs to be done in the tracer? Do you know where I can get more information on this?
Regards,
Mattias
-----Ursprungligt meddelande-----
Fr?n: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] F?r xxxxx@gmail.com
Skickat: den 30 oktober 2007 13:03
Till: Windows System Software Devs Interest List
?mne: RE:[ntdev] DbgPrint, &!STATUS!
%!STATUS! is used by the trace viewers and not understood by DbgPrint.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer