OutputDebugStringA limitation used to be close to 4K, but with OutputDebugStringW, what is the limitation?
Posted by jpluimers on 2020/12/31
I wonder what the limitation of OutputDebugStringW is, as OutputDebugStringA had a limit imposed by the DBWIN_BUFFER which was 4K (minus a bit overhead):
- [WayBack] OutputDebugString function (Windows)
- [Archive.is] A Debugging Approach to OutputDebugString – Rubato and Chord (as [WayBack] blogs.msdn.microsoft.com/reiley/2011/07/29/a-debugging-approach-to-outputdebugstring/ is gone)
- [WayBack] Understanding OutputDebugString – The Imaginary Road
- [WayBack] Understanding Win32 “OutputDebugString”
- [WayBack] Windows 10: New Anti-Debug OutputDebugStringW | ntquery
- [WayBack] Visual Studio Output Window Error – C++ – Stack Overflow
- [WayBack] Perfect imprecision, thoughts on memory leaks, performance profiling, code coverage, deadlock detection and flow tracing » The cost of using OutputDebugString
–jeroen
Leave a Comment