Crash on Windows with core.stdc.stdlib.free()

[ketmar via Digitalmars-d-learn]

On Wed, 12 Nov 2014 16:03:08 +0000
Chris via Digitalmars-d-learn <digitalmars-d-learn at puremagic.com> wrote:

> On Wednesday, 12 November 2014 at 14:42:34 UTC, Chris wrote:
> > On Wednesday, 12 November 2014 at 14:26:15 UTC, ketmar via
> >> if you can extend C DLL, just add wrapper for `free()` there. 
> >> so you
> >> will not call `free()` from D, but call C DLL function which 
> >> will free
> >> the memory. it's a good practice anyway, 'cause it's 
> >> recommended to
> >> free memory in the same library where you allocated it.
> >
> > I initially had an implementation that did exactly that (I 
> > usually do that), but for some reason it didn't work properly 
> > in this particular case and caused all sorts of undefined 
> > behavior. But I'll have a look at it again.
> 
> I've changed the code so that the memory is freed in C. Although 
> it works "better" it crashes too every now and then
> 
> (WindowsError : exception : access violation writing 0x0310A1B4)
> 
> Will look into it.
this also can happen due to allocators conflict somehow. or due to
other code which stores the pointer somewhere and then accesses the
memory. i think that it will be hard to trace without debugger.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-learn/attachments/20141112/63b4d7db/attachment.sig>