Re: Where do you go after FinalRelease?
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Wed, 6 Sep 2006 12:42:41 -0400
Dave <dave5398@xxxxxxxxxxxxxx> wrote:
"Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
news:uik4U1S0GHA.772@xxxxxxxxxxxxxxxxxxxxxxx
Your destructor executes right after FinalRelease. It in turnAlexander, not sure how to do that. I am using a VB front end so I
invokes the destructors of all member variables and base
classes.
Set the exception for Access Violation to break into the
debugger when thrown. This will give you the exact place
where the exception occurs.
use VB as the debugging programme.
You can run VB IDE itself under VC's debugger.
When I get an exception it goes
into the window with assembler which means nothing to me then it
tells me that VB has no debgging information so I am none the wiser.
Look at the call stack when you are dropped into the debugger. If you
are lucky, your DLL's code is somewhere on the stack.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- References:
- Where do you go after FinalRelease?
- From: Dave
- Re: Where do you go after FinalRelease?
- From: Alexander Nickolov
- Re: Where do you go after FinalRelease?
- From: Dave
- Where do you go after FinalRelease?
- Prev by Date: Re: test container works, explorer embedding sortof works
- Next by Date: Re: Where do you go after FinalRelease?
- Previous by thread: Re: Where do you go after FinalRelease?
- Next by thread: Re: Where do you go after FinalRelease?
- Index(es):
Relevant Pages
|