-
March 26th, 2014, 03:25 PM
#1
Some inconveniences when using OutputDebugString
When I dump some information to the output console,
it is mixed along with the system messages.
Are there anyways that I can separate them into 2 output windows?
Thanks
Jack
Last edited by lucky6969b; March 26th, 2014 at 03:25 PM.
Reason: typo
-
March 26th, 2014, 05:29 PM
#2
Re: Some inconveniences when using OutputDebugString
The alternative that I know of (and use) is to use DebugView with a specific filter applied.
gg
-
March 26th, 2014, 05:35 PM
#3
Re: Some inconveniences when using OutputDebugString
Thanks, I'll try it out today.
Jack
-
March 26th, 2014, 11:38 PM
#4
Re: Some inconveniences when using OutputDebugString
Hello, back in here.
OS: windows 7 x64 ultimate SP1
Compiler: Visual Studio 2010 Ultimate with SP1
http://technet.microsoft.com/en-us/s.../bb896647.aspx
I just tried it this afternoon, and discovered that it can't capture x64 applications debug strings.
Just tried it, but the official site says it does work for x64. Just don't understand why.
Thanks
Jack
-
March 27th, 2014, 12:35 AM
#5
Re: Some inconveniences when using OutputDebugString
I don't think debug view works while a debugger is attached. Forgot about that.
gg
-
March 27th, 2014, 12:42 AM
#6
Re: Some inconveniences when using OutputDebugString
Okay, it works now....
Thanks
Jack
-
March 27th, 2014, 07:33 AM
#7
Re: Some inconveniences when using OutputDebugString
alternatively, you can (conditionally) create a console window explicitely (even in a GUI app) via AllocConsole (can only have 1 per process).
and instead of using outputdebugstring write your (debug) output to that console specifically.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|