Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
How To: Output Trace string on machine where Visual Studio is not installed
| Article ID | : | 949885 |
| Last Review | : | February 29, 2008 |
| Revision | : | 1.2 |
Source: Microsoft Support
Back to the top
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Back to the top
Action
You have created an application with trace messages (for instance, using
OutputDebugString (http://msdn2.microsoft.com/en-us/library/aa363362.aspx)), but need to test it on a machine where Visual Studio is not installed, and wish to see the debug strings somehow.
Back to the top
Result
The application runs, but there is no output window that displays the debug strings.
Back to the top
Cause
OutputDebugString and
DbgPrint (http://msdn2.microsoft.com/en-us/library/ms792790.aspx) (and other macros that ultimately wrap these API functions) direct their output to a debugger. If one is not installed, the output is not sent anywhere.
Back to the top
Resolution
Install a debugger. Microsoft provides the powerful WinDbg debugger at no charge, and it can be used to view the debug string outputs. There are also third-party utilities which can be purchased to provide this output (Use Live Search to locate others).
For the WinDbg solution, follow these steps:
1. Install
Debugging Tools for Windows (http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx) on the machine where you wish to test.
2. This will install WinDbg in the folder where debugging tools are installed.
3. Go to folder debugging tools for windows and open WinDbg.
4. Do one of the following:
| • | Launch the executable externally, then in WinDbg go to File->Attach to Process. |
| • | Launch the executable from within WinDbg, using File->Open Executable. |
5. Type g command in WinDbg to resume execution.
6. Now you can see trace statements in WinDbg’s screen.
Back to the top
More Information
Reading and Filtering Debugging Messages (http://msdn2.microsoft.com/en-us/library/ms792789.aspx)Trace Listeners (http://msdn2.microsoft.com/en-us/library/4y5y10s7.aspx)Event Tracing (Windows) (http://msdn2.microsoft.com/en-us/library/bb968803.aspx)Back to the top
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Back to the top
APPLIES TO
| • | Microsoft Visual Studio .NET 2003 Professional Edition |
| • | Microsoft Visual Studio .NET 2003 Enterprise Developer |
| • | Microsoft Visual Studio .NET 2003 Enterprise Architect |
| • | Microsoft Visual Studio 2005 Professional Edition |
| • | Microsoft Visual Studio 2005 Team Edition for Software Architects |
| • | Microsoft Visual Studio 2005 Team Edition for Software Developers |
| • | Microsoft Visual Studio 2005 Team Suite |
| • | Microsoft Visual Studio 2008 Professional Edition |
| • | Microsoft Visual Studio Team System 2008 Architecture Edition |
| • | Microsoft Visual Studio Team System 2008 Development Edition |
| • | Microsoft Visual Studio Team System 2008 Team Suite |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
