Re: VB crash - Can anybody read a memory dump?
- From: "expvb" <nobody@xxxxxxx>
- Date: Sun, 18 May 2008 12:35:01 -0400
Besides what Ralph suggested, here is a method to pinpoint the cause of a
crash in a compiled VB6 app using VC++:
- In VB6, in the project's properties, go to the Compile tab and select
"Create symbolic debug info". This will create a PDB file when you compile
your project.
- Save and Compile.
- Run the EXE from Windows Explorer.
- Go to VC++ 6.0|File|Close Workspace.
- Go to Build|Start Debug|Attach to process, and select your running EXE.
- Go to View|Debug Windows, and make sure that "Call Stack" window is
visible.
- Let it crash.
- The call stack shows you where the problem is. One of the lines will point
to your source code, when you double click on that, it will show you the
source code and points to the exact line that caused the error.
- If the program closed normally, or you want to try again, go to
Build|Execute <Your EXE file name>, then use "Attach to process" again.
- There are some settings that you could change, if necessary, in
Project|Settings|Debug.
See also:
How to debug a native code Visual Basic Component in Visual C++
http://support.microsoft.com/kb/166275/EN-US/
How To Debug a Visual Basic Out-of-Process Server with Visual C++
http://support.microsoft.com/kb/200034/en-us
Make sure that you disable "Create symbolic debug info" before releasing
your software.
.
- Follow-Ups:
- Re: VB crash - Can anybody read a memory dump?
- From: Patrick Wetering
- Re: VB crash - Can anybody read a memory dump?
- References:
- VB crash - Can anybody read a memory dump?
- From: Patrick Wetering
- VB crash - Can anybody read a memory dump?
- Prev by Date: Re: Rapid gfx display Qs
- Next by Date: Making API TypeLib
- Previous by thread: Re: VB crash - Can anybody read a memory dump?
- Next by thread: Re: VB crash - Can anybody read a memory dump?
- Index(es):
Relevant Pages
|