<div>
<div class="content wysiwyg-content">
We have an application that runs fine under Windows NT. &nbsp;When run under win32s in Windows 3.1, it crashes at random, non repeatable times. &nbsp;We need a tool that can produce essentially a core file, or some type of stack dump at the time of death, so that we can analyze what happened. &nbsp;Is there such a tool? &nbsp;I've seen a utility that ships with Lotus Notes (qnc.exe, Quincy), that does this under OS/2, NT, and possibly others, for Lotus Notes crashes. &nbsp;It provides, in a &quot;notes.rip&quot; text file, a dissection of the stack, so that you can tell what the call stack was at the time of death. &nbsp;(It's invaluable for programming notes server add-ins). &nbsp;I need something similar that I can use on/compile into, my own applications.<br />
<br />
Any suggestions?<br />

</div>
</div>


We have an application that runs fine under Windows NT.  When run under win32s in Windows 3.1, it crashes at random, non repeatable times.  We need a tool that can produce essentially a core file, or some type of stack dump at the time of death, so that we can analyze what happened.  Is there such a tool?  I've seen a utility that ships with Lotus Notes (qnc.exe, Quincy), that does this under OS/2, NT, and possibly others, for Lotus Notes crashes.  It provides, in a "notes.rip" text file, a dissection of the stack, so that you can tell what the call stack was at the time of death.  (It's invaluable for programming notes server add-ins).  I need something similar that I can use on/compile into, my own applications.

Any suggestions?


Any good crash debug tools for win32s apps?

Most development for the Microsoft platform is done utilizing the technologies supported by the.NET framework. Other development is done using Visual Basic for Applications (VBA) for programs like Access, Excel, Word and Outlook, with PowerShell for scripting, or with SQL for large databases.