🚀 go-pugleaf

Sorry guys, I was not very sure of which group to post it to.
Thank you for conveying that language.cpp is the right one.

"Remy Lebeau (TeamB)" <gambit47@yahoo.com> wrote in message
news:3dd0bae3@newsgroups.borland.com...
> "rinu chacko" <rinu@smartedge.net> wrote in message
> news:3dd0b4b5@newsgroups.borland.com...
>
> Please don't cross-post, it is against Borland's newsgroup guidelines.
Only
> post questions to the single most appropriate group, which in this case
> would be the .language.cpp group.
>
> > Now the application crashes during disposing of some
> > dynamically allocated memory, which is declared in
> > DLL1, allocated in DLL2 and being disposed from
> > DLL1.
>
> You shouldn't be allocating the memory in one place and freeing it
> elsewhereacross different modules.  You should free the memory from the
same
> module that is was allocated from.  This insures that the memory manager
> that allocated the memory is the same one that frees it correctly.
>
> > - We create TStLlist (systools list object - turbopower library) object
in
> > DLL1, and pass it to DLL2.
> > - Within DLL2, the list getting filled.
> > - Back in DLL1, we clear the list. During this it crashes.
>
> How exactly does DLL2 fill the list?  Is it allocating any of its own
> dynamic memory for the items?  If so, you should be using DLL2 to free
them,
> not DLL1.  DLL1 allocated the memory for the list itself, not the items.
It
> should only free the list itself, after DLL2 has had a chance to free the
> items it allocated.
>
>
> Gambit
>
>