🚀 go-pugleaf

Hi Remy,

I have create a program act as either Video Server or Client.
where the Server can close the client exe remotely. It had 2 main
portion, EXE and DLL, DLL was a form with DsPack component
written in C++Builder 5 and EXE in C++Builder4.

The problem almost every time (99%) had problem when close the
application remotely, by issue the PostMessage with WM_CLOSE or
Close.  Where the application always access/call/jump to the
free-ed DLL memory/code area (filled with 0 or ???? view with debugger),
where I'm not sure the code belonging to which lib, bcoz the
debugging show the wrong source code or little info.

The problem will not happen if it was Close by click the Window 'X' button
or press Alt-F4 on the client PC.

But I have just tested with PostMessage with WM_CLOSE and
WM_DESTROY, the problem look like dissapeared.

What is the different, if just WM_CLOSE with WM_CLOSE and
WM_DESTROY?

Regards
KL Chin

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:41c79929$3@newsgroups.borland.com...
>
> "KL Chin" <klchin@1asia.com.my> wrote in message
> news:41c78d36@newsgroups.borland.com...
>
>> Everything were fine until it going to close the application, where
>> it receive a signal from remote PC, either with WM_CLOSE.or
>> Close. At this closing process, this form will call main EXE to
>> unload the DLL later.   The problem was where free-ed code area
>> always access/call-back again.
>
> Please clearify.
>
>
> Gambit
>
>