This kind of exception is horrible. I've had it a
couple of times, in different circumstances, so while I can't comment on your
exact situation maybe I can at least point you in the right
direction.
When this has happened to me, it usually boils down
to something being accessed that has already been freed. For example, a form
that was created with Application.CreateForm was freed manually elsewhere and
then the app raised an exception when it exited. Perhaps you have code that is
trying to reference the form after it is freed? Alternatively, this type of
error also manifests sometimes if you are passing strings back and forth with
the DLL and you don't have sharemem as the first unit in the uses
clause.
Maybe helpful, maybe not.
Phil.
|
- [DUG]: DLLs Aaron Scott-Boddendijk
- RE: [DUG]: DLLs Cooke, Andrew
- [DUG]: DLLs Aaron Scott-Boddendijk
- Re: [DUG]: DLLs Aaron Scott-Boddendijk
- RE: [DUG]: DLLs Cooke, Andrew
- Re: [DUG]: DLLs Aaron Scott-Boddendijk
- [DUG]: DLLs Robert Martin
- RE: [DUG]: DLLs Jim Zheng
- Re: [DUG]: DLLs Robert Martin
- Re: [DUG]: DLLs Phil Middlemiss
- Re: [DUG]: DLLs Robert Martin
- RE: [DUG]: DLLs Myles Penlington
- RE: [DUG]: DLLs Myles Penlington
- Re: [DUG]: DLLs Robert Martin