Feature #4553 2009-03-29 19:18
xoft
Log OutputDebugString() output
When a debugged Windows app calls OutputDebugString() call, gdb writes a Warning to the "Debugger (debug)" console. Currently, C:B ignores it. Is there a simple way to make this Warning seen in the Debugger window?
- Category
- Debugging
- Status
- Open
- Close date
- Assigned to
History
This is not feature request for CB, but for GDB.
-> ollydbg: I don't think so, GDB already processes these and sends them to stdout, only CB doesn't copy them from stdout to the Debugger window.
Hi.
Did you mean that these "string" can be shown in Debugger(debug) panel, and not shown in debug panel?
That can be solved if you can CB filter these string. I think it is not too hard to implement it.
Yes, exactly that.
When program executes OutputDebugStringA ("mydebug"); GDB writes to stdout: "warning: mydebug" CB catches that text in the Debugger (debug) panel, but doesn't display it in the Debugger panel. Problem with implementing that is that the GDB message is too generic, it writes some other warnings in the same way. Example: --- warning: Lowest section in C:\Windows\system32 \normaliz.dll is .text at 00401000 warning: Program start warning: starting engine... --- The second and third warnings are from my program, the first warning is from somewhere else in GDB.
I suppose it'd be best first to request MinGW/GDB devs to modify the OutputDebugString() output format, then add support in CB for the new format; but still an option to see all GDB warnings could be useful, too.