none
WPP tracing via WinDbg RRS feed

  • Question

  • I'm currently using WPP tracing for debugging and getting trace logs from my NDIS miniport driver. Traceview did get log some prints during initialization when there was some failure while there were mistakes when registering interrupt. But now I am getting no trace logs when there is a crash when miniport initialization completes and the NDIS miniport driver receives some network discovery packets from the protocol driver.

    The crash is caused by my driver as I'm writing into a wrong location. I wanted to print by base address and offset values for debugging purposes. I'm kind of stuck at the moment but for stack traces providing the values being passed to the functions. Is there a way to get the WPP prints on a WinDbg connected using 1394 cable? Any other suggestions also would be much appreciated. 

    With regards, Jenson Alex Pais

    Thursday, September 1, 2016 9:14 AM

Answers

  • Jenson,  

         Follow the directions for !wmitrace that is all you should need (except enabling things with logman). 

          I mentioned the macros since there are still references (some of which I wrote), but unfortunately while it was a really nice feature, Microsoft trashed it.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    • Marked as answer by JENSON PAIS Thursday, September 22, 2016 2:27 PM
    Thursday, September 1, 2016 1:02 PM

All replies

  • Take a look at !wmitrace https://msdn.microsoft.com/en-us/library/windows/hardware/ff561362(v=vs.85).aspx this may help you. 

    When WPP tracing was announced there was an easy way to have the output also go through KdPrint via the definition of a C preprocessor macro, but since then each version of WPP tracing has required additional tweaks to make it work.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    Thursday, September 1, 2016 12:22 PM
  • Don,

    So I need to use to logman to create  a log on the target machine and use the WinDbg/KD to get the prints using the additional tweaks that you mentioned ? 

    I'll look into the !wmitrace commands and see if they are of help or not. I tried !wmitrace.bufdump but it didn't show trace messages from my miniport. Do I need to have .tmf files on the host side then ?

    Cheers for the inputs. 


    With regards, Jenson Alex Pais

    Thursday, September 1, 2016 12:53 PM
  • Jenson,  

         Follow the directions for !wmitrace that is all you should need (except enabling things with logman). 

          I mentioned the macros since there are still references (some of which I wrote), but unfortunately while it was a really nice feature, Microsoft trashed it.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    • Marked as answer by JENSON PAIS Thursday, September 22, 2016 2:27 PM
    Thursday, September 1, 2016 1:02 PM