Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 949517 - Last Review: February 21, 2008 - Revision: 1.2
Stack Size Monitoring Tools
Source: Microsoft Support
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.
Monitor stack size to prevent, predict or debug the StackOverflowException.
The following tools can be used to view the current stack size for threads:
1)Â Visual studio debugger.
2) WinDBG
3) Process Explorer
The need to monitor and diagnose potential stack overflow problems during the software development and testing stage is due to the catastrophic nature of the stack overflow condition.  This exception or state can rarely be handled intelligently and often cannot be handled at all. For these reasons, it can be desirable to detect or monitor thread stack size during application development and testing, or debugging, when the potential for too-little stack space exists, or stack overflow errors are detected.
See the windbg help documentation under the heading, Debugging a Stack Overflow, for a detailed example of debugging thread stack size issues on a native debugger.
Debugging Tools for Windows
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
(http://www.microsoft.com/whdc/devtools/debugging/default.mspx)
Managed StackOverflowException Class:
http://msdn2.microsoft.com/en-us/library/system.stackoverflowexception.aspx
(http://msdn2.microsoft.com/en-us/library/system.stackoverflowexception.aspx)
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.
APPLIES TO
- Microsoft Visual Studio .NET 2002 Professional Edition
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio 2005 Standard Edition
- Microsoft Visual Studio 6.0 Enterprise Edition
- Microsoft Visual Studio 2008 Professional Edition
- Microsoft Visual Studio 2005 Team Edition for Software Developers
| kbnomt kbrapidpub kbmbsdevelopmenttools KB949517 |
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
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please