Prev: EngMapFile vs. CreateFileMapping - filename differences
Next: USB transfer not working after 6 incomplete IN transactions
From: Tim Roberts on 29 Jan 2009 23:35
"nicolasr" <nicolasrREMOVETHISSPAMBLOCKER(a)gmx.net> wrote:
>
>can anyone give me a hint on how to make _DbgPrintF
>in ksdebug.h print out messages on Vista?
>
>I'm using DebugView to capture kernel messages.
>With my own macro
>
>#define DebugPrint(_x_) \
> DbgPrint("MYDRIVER.SYS: ");\
> DbgPrint _x_;
>
>I get debug messages. But not from code that uses
>_DbgPrintF, which is defined in ksdebug.h as:

This is not that hard to figure out, is it? In ONE of your files, do
#define KSDEBUG_INIT
before
#include <ksdebug.h>

By doing that and nothing else, you'll see TERSE and ERROR level prints. If
you want ALL prints, define:
#define DEBUG_LEVEL DEBUGLVL_BLAB
#define KSDEBUG_INIT
#include <ksdebug.h>
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: nicolasr on 30 Jan 2009 07:16

> This is not that hard to figure out, is it? In ONE of your files, do
> #define KSDEBUG_INIT
> before
> #include <ksdebug.h>
>

that's what I thought too, but it gives error C2220 because of
redefinition.
I have now found the earlier definition of DEBUG_LEVEL
in the 'sources' file. The confusion was caused by Windows
Search. I almost searched my entire disk for the definiton
of DEBUG_LEVEL but the 'sources' files seems never have
been included, probably because there's no search rule for it.
Sorry for my ignorance :-)

thanks,
Nick
From: Maxim S. Shatskih on 31 Jan 2009 05:59
> I have now found the earlier definition of DEBUG_LEVEL
> in the 'sources' file. The confusion was caused by Windows
> Search.

This amazingly bad tool creates more confusion then good. Maybe it is OK to be used on Word/Excel documents, but for searching _code_ "Find in Files" in VS or the port of GNU grep is much better.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: nicolasr on 31 Jan 2009 11:00
>This amazingly bad tool creates more confusion then good. Maybe it is OK to
>be used on Word/Excel documents, >but for searching _code_ "Find in Files"
>in VS or the port of GNU grep is much better.

thanks, grep looks good. I will try that in the future...
Nick

First  |  Prev  | 
Pages: 1 2
Prev: EngMapFile vs. CreateFileMapping - filename differences
Next: USB transfer not working after 6 incomplete IN transactions