suryamp / dokan

Automatically exported from code.google.com/p/dokan
0 stars 0 forks source link

Debug output present in release builds #186

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open Sysinternals DebugView
2. Take note of DokanDispatchIoControl output

What is the expected output? What do you see instead?
Should see nothing.

What version of the product are you using? On what operating system?
0.5.3

Please provide any additional information below.
Suggest making DDbgPrint, OutputDebugString, etc. macros that become nulled 
when compiling release builds. Dokan output is making a mess of my debugging.

Original issue reported on code.google.com by rafael.r...@gmail.com on 12 Sep 2010 at 4:38

GoogleCodeExporter commented 9 years ago
Is this not to do with the Debug flag that is passed into the Dokan mounter ?
 OutputDebugString is never compiled to null..

Original comment by smurf...@gmail.com on 25 Sep 2010 at 7:39

GoogleCodeExporter commented 9 years ago
Use the stderr flag as the code internally does this:

   if (g_UseStdErr)
      fwprintf(stderr, buffer);
   else
      OutputDebugStringW(buffer);

Original comment by smurf...@gmail.com on 11 May 2012 at 8:14