From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Interfaces.C.Strings chars_ptr memory management strategy
Date: Sun, 3 Jun 2018 21:33:17 +0200
Date: 2018-06-03T21:33:17+02:00 [thread overview]
Message-ID: <pf1fps$4rv$1@gioia.aioe.org> (raw)
In-Reply-To: 735fd76c-c0a7-4e8c-a534-857772cada9b@googlegroups.com
On 2018-06-03 20:31, ytomino wrote:
> Perhaps, malloc is better than New_String in this case.
>
> function malloc (s : Interfaces.C.size_t) return Interfaces.C.Strings.chars_ptr
> with Import, Convention => C;
I had a case when that caused the application crashed.
I guess it was because of mixed Visual Studio and GCC run-times. The
pointer returned by the malloc from one was freed in a third-party C
library by another.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
next prev parent reply other threads:[~2018-06-03 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 22:22 Interfaces.C.Strings chars_ptr memory management strategy NiGHTS
2018-05-26 2:52 ` Shark8
2018-05-26 12:44 ` NiGHTS
2018-05-26 13:56 ` Shark8
2018-05-30 13:10 ` Alejandro R. Mosteo
2018-05-30 19:56 ` Randy Brukardt
2018-05-31 10:34 ` Alejandro R. Mosteo
2018-05-31 22:25 ` Randy Brukardt
2018-06-05 12:42 ` Alejandro R. Mosteo
2018-06-03 18:31 ` ytomino
2018-06-03 19:33 ` Dmitry A. Kazakov [this message]
2018-06-03 20:03 ` ytomino
2018-06-04 7:06 ` Dmitry A. Kazakov
2018-06-04 7:47 ` ytomino
2018-06-03 20:37 ` ytomino
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox