On Apr 10, 2011, at 3:38 PM, Jonas Maebe wrote:
>
> On 10 Apr 2011, at 15:02, Darius Blaszyk wrote:
>
>> You're right that there seems to be a memleak somewhere, but it's something
>> strange, heaptrc reports 1 unfreed block and 0bytes unfreed. Never seen this
>> before.
>
> It's because you
On 10 Apr 2011, at 15:02, Darius Blaszyk wrote:
> You're right that there seems to be a memleak somewhere, but it's something
> strange, heaptrc reports 1 unfreed block and 0bytes unfreed. Never seen this
> before.
It's because you have memory corruption. Then heaptrc cannot give accurate
sta
On Apr 10, 2011, at 12:24 AM, Jonas Maebe wrote:
>
> On 10 Apr 2011, at 00:20,
> wrote:
>
>> I get strange errors when using GetMem. In my
>> app I keep on allocating and freeing memory in a variable. At a certain
>> moment I do keep getting a SIGSEGV on the GetMem call when trying to
>> all
On 10 Apr 2011, at 00:20,
wrote:
> I get strange errors when using GetMem. In my
> app I keep on allocating and freeing memory in a variable. At a certain
> moment I do keep getting a SIGSEGV on the GetMem call when trying to
> allocate exactly 128bytes. However allocating other sizes seems to
ZeelandNet Webmail
I get strange errors when using GetMem. In my
app I keep on allocating and freeing memory in a variable. At a certain
moment I do keep getting a SIGSEGV on the GetMem call when trying to
allocate exactly 128bytes. However allocating other sizes seems to work
just fine. Is
