StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow can I guarantee catching a EXCEPTION_STACK_OVERFLOW structured exception in C++ under Visual Studio 2005?
primarykey
Id
436671
data
AcceptedAnswerId
438852
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-12T19:28:28.340
FavoriteCount
4
LastActivityDate
2012-07-03T14:51:14.683
LastEditDate
2009-01-12T22:10:19.793
LastEditorUserId
28950
OwnerUserId
28950
ParentId
0
PostTypeId
1
Score
6
ViewCount
2432
LastEditorDisplayName
Aaron
text
Body
<h3>Background</h3> <ul> <li>I have an application with a <em>Poof-Crash</em>[<em>1</em>]. I'm fairly certain it is due to a blown stack. </li> <li>The application is Multi-Threaded. </li> <li>I am compiling with "<code>Enable C++ Exceptions: Yes With SEH Exceptions (/EHa)</code>".</li> <li>I have written an SE Translator function and called <code>_set_se_translator()</code> with it.</li> <li>I have written functions for and setup <code>set_terminate()</code> and <code>set_unexpected()</code>.</li> <li>To get the Stack Overflow, I must run in release mode, under heavy load, for several days. Running under a debugger is not an option as the application can't perform fast enough to achieve the runtime necessary to see the issue.</li> <li>I can simulate the issue by adding infinite recursion on execution of one of the functions, and thus test the catching of the <code>EXCEPTION_STACK_OVERFLOW</code> exception.</li> <li>I have WinDBG setup as the crash dump program, and get good information for all other crash issues but <strong>not this one</strong>. The crash dump will only contain one thread, which is 'Sleep()'ing. All other threads have exited.</li> </ul> <h3>The Question</h3> <p>None of the things I've tried has resulted in picking up the <code>EXCEPTION_STACK_OVERFLOW</code> exception. </p> <p>Does anyone know how to guarantee getting a a chance at this exception during runtime in release mode?</p> <h3>Definitions</h3> <ol> <li><em>Poof-Crash</em>: The application crashes by going "poof" and disappearing without a trace.</li> </ol> <p><em>(Considering the name of this site, I'm kind of surprised this question isn't on here already!)</em></p> <h3>Notes</h3> <ol> <li>An answer was posted briefly about adjusting the stack size to potentially force the issue sooner and allow catching it with a debugger. That is a clever thought, but unfortunately, I don't believe it would help. The issue is likely caused by a corner case leading to infinite recursion. Shortening the stack would not expose the issue any sooner and would likely cause an unrelated crash in validly deep code. Nice idea though, and thanks for posting it, even if you did remove it.</li> </ol>
Tags
<c++><debugging><exception-handling><stack-overflow><structured-exception>
Title
How can I guarantee catching a EXCEPTION_STACK_OVERFLOW structured exception in C++ under Visual Studio 2005?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAaron
UserOwnerUserId
1. USAaron
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.