Home > Archive > Clarion > March 2004 > Multi Dll - Memory Stack Overflow
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Multi Dll - Memory Stack Overflow
|
|
| Marin Kaluza 2004-03-29, 2:30 am |
| I have some apps i C55. When I start them and compile in C6, then execute,
everything is working properly, but when I close window called as external
procedure from onother app which make thread, my app gets GPF.
Is there anybody who could help me.
| |
| Ivo Ivanov 2004-03-29, 5:30 am |
| Hi Marin,
I had the same problem.
Is your data DLL (I guess you have one) mutually linked with another DLL? If
so this is the reason.
The solution is simple. First make a DLL that exports the data definitions
and does not do anything else and does not use any other DLLs from your app.
Make sure that all the links between the exe and dlls are defined as
"external DLL". In case you have external modules defined as "external lib"
change them to "external DLL". If you use Translator class (this is an
option in the procedure's properties) remove it.
success,
Ivo Ivanov
Modest Automatisering B.V.
Holland
"Marin Kaluza" <mkaluza@veleri.hr> schreef in bericht
news:c48fmf$t6e$1@bagan.srce.hr...
> I have some apps i C55. When I start them and compile in C6, then execute,
> everything is working properly, but when I close window called as external
> procedure from onother app which make thread, my app gets GPF.
>
> Is there anybody who could help me.
>
>
| |
| Marin Kaluza 2004-03-29, 11:30 am |
| Thanks it works.
Marin
"Ivo Ivanov" <iivanov@modest.nl> wrote in message
news:4067ec98$0$33071$6c56d894@diablo.nl.easynet.net...
> Hi Marin,
>
> I had the same problem.
> Is your data DLL (I guess you have one) mutually linked with another DLL?
If
> so this is the reason.
> The solution is simple. First make a DLL that exports the data definitions
> and does not do anything else and does not use any other DLLs from your
app.
> Make sure that all the links between the exe and dlls are defined as
> "external DLL". In case you have external modules defined as "external
lib"
> change them to "external DLL". If you use Translator class (this is an
> option in the procedure's properties) remove it.
>
> success,
>
> Ivo Ivanov
> Modest Automatisering B.V.
> Holland
>
> "Marin Kaluza" <mkaluza@veleri.hr> schreef in bericht
> news:c48fmf$t6e$1@bagan.srce.hr...
execute,[color=darkred]
external[color=darkred]
>
>
|
|
|
|
|