{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 唯我独甜 的问题《Overhead associated with OutputDebugString in rele》','https://www.manongdao.com/q-1203346.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is there a significant overhead associated with calling OutputDebugString in release build?
相关问题
- the application was unable to start correctly 0xc0
- Faster loop: foreach vs some (performance of jsper
- Inheritance impossible in Windows Runtime Componen
- how to get running process information in java?
- Why wrapping a function into a lambda potentially
相关文章
- 如何让cmd.exe 执行 UNICODE 文本格式的批处理？
- 怎么把Windows开机按钮通过修改注册表指向我自己的程序
- how do I log requests and responses for debugging
- Warning : HTML 1300 Navigation occured?
- Bundling the Windows Mono runtime with an applicat
- Windows 8.1 How to fix this obsolete code?
- Why windows 64 still makes use of user32.dll etc?
- DOM penalty of using html attributes
Never leave OutputDebugString() calls in a release build. Always either remove them by using #ifdef statements, or provide another switch to have them turned off.
If you leave them in, have them disabled by default and only activate them on request, because otherwise your app will make it hard to debug other apps which behave nice (i.e., only output debug data on request).
Theres DebugView to catch the output of apps, but of course that's only good if not every app chatters along for no good reason.