Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > Miscellaneous Utilities
  New Posts New Posts RSS Feed: DbgView Filter
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

DbgView Filter
 Post Reply Post Reply
Author
Message Reverse Sort Order
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Online Status: Offline
Posts: 17492 		Post Options Post Options   Quote molotov Quote  Post ReplyReply Direct Link To This Post Topic: DbgView Filter
    Posted: 14 November 2009 at 8:38pm
Apparently none of the customers are large enough to cause the companies to change the app to be more configurable so as not to produce the output in such a fashion... Dead

You might give the workaround a try - you could even use Dependency Walker to profile the app, as a test...  Another option would be to patch the app or hook OutputDebugStringA / OutputDebugStringW, and not call the hooked function in the replacement or perhaps do some filtering in the replacement function's implementation, to only call the hooked function in certain cases...
Daily affirmation:
net helpmsg 4006
Back to Top
bob8500 View Drop Down
Newbie
Newbie


Joined: 03 November 2009
Online Status: Offline
Posts: 2 		Post Options Post Options   Quote bob8500 Quote  Post ReplyReply Direct Link To This Post Posted: 05 November 2009 at 5:10pm

Thanks for the reply.

Can't turn the debug output off for this app. We contacted the vendor and they essentially said "deal with it, it's debug".

What is really causing the problem is that another app we are using is uses debug output for its application logging. They have absolutely no intention of changing their app, just as the "prefix debug output with a *" company has no intention of changing theirs either.
 
btw, these are big companies selling to 100's of large corporate customers... 
Back to Top
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Online Status: Offline
Posts: 17492 		Post Options Post Options   Quote molotov Quote  Post ReplyReply Direct Link To This Post Posted: 04 November 2009 at 4:27am
Hi bob8500,

A few thoughts...
I'm not aware of a way to indicate to DbgView to exclude lines containing a '*' as that character is the wildcard - specifying it in the Exclude filter will exclude all output.

Does the application in question have some configuration that can be used to turn the debug logging down or even off?  Have you made the application maker aware of the problem?  Perhaps some update may be available?

If the application is running under a debugger, DbgView will not get the output.  So a hackish workaround may be to run the app with a debugger attached.  Something like Dependency Walker, with all boxes on the Profile dialog checked, would do it, or you could write a simple debugger that basically launched the application with the DEBUG_PROCESS flag passed to CreateProcess, and simply called WaitForDebugEvent / ContinueDebugEvent in the debugger loop...
Daily affirmation:
net helpmsg 4006
Back to Top
bob8500 View Drop Down
Newbie
Newbie


Joined: 03 November 2009
Online Status: Offline
Posts: 2 		Post Options Post Options   Quote bob8500 Quote  Post ReplyReply Direct Link To This Post Posted: 03 November 2009 at 2:42pm
A shrink-wrap application recently deployed in our environment is writing so much debug output that it has made what used to be a very useful log created by DbgView almost unusable. The only filter/pattern that we can come up with to filter out this debug spam is the character "*" in the very first character position.
 
Is there a way to apply a negative filter that will filter these out? It does not appear that DbgView filters are regular expressions, otherwise I think ^\* would do what we want.
 
Thanks.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down