On Sunday 21 October 2007 10:54:16 Bram Geron wrote:
> chromatic wrote:
> > Seems reasonable to me. How did you check for leaks, by the way?
> I ran the test file for two minutes (it's an infinite loop), and top
> showed no change in memory use. I assumed that was accurate enough :)
Sounds rig
chromatic wrote:
> On Sunday 21 October 2007 07:57:58 Bram Geron wrote:
>
>> Attached patch fixes the segfault for me. (And no memory leak too.) The
>> problem was that mark_context didn't mark ctx->caller_ctx, which is used
>> in get_params. Usually the caller context is accessible through
>> cur
On Sunday 21 October 2007 07:57:58 Bram Geron wrote:
> Attached patch fixes the segfault for me. (And no memory leak too.) The
> problem was that mark_context didn't mark ctx->caller_ctx, which is used
> in get_params. Usually the caller context is accessible through
> current_cont->to_ctx, but in
Will Coleda wrote:
>
> On Sep 10, 2007, at 12:47 AM, chromatic wrote:
>
>> On Sunday 09 September 2007 21:40:56 Will Coleda via RT wrote:
>>
>>>
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: KERN_INVALID_ADDRESS at address: 0xdeadbef3
>>> 0x00010b42 in clone_key
On Sep 10, 2007, at 12:47 AM, chromatic wrote:
On Sunday 09 September 2007 21:40:56 Will Coleda via RT wrote:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xdeadbef3
0x00010b42 in clone_key_arg (interp=0x31003b0, st=0xbfffef3c) at
On Sunday 09 September 2007 21:40:56 Will Coleda via RT wrote:
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0xdeadbef3
> 0x00010b42 in clone_key_arg (interp=0x31003b0, st=0xbfffef3c) at
> src/inter_call.c:641 641 if (key &&
On Sun Jun 03 20:33:35 2007, [EMAIL PROTECTED] wrote:
> On Saturday 28 April 2007 16:43:06 Mehmet Yavuz Selim Soyturk wrote:
>
> > Next program makes a slurpy tailcall, and it causes a memory leak
> for me.
>
> Confirmed. Interestingly, the problem looks like a Key PMC somewhere
> gets
> garbage
On Saturday 28 April 2007 16:43:06 Mehmet Yavuz Selim Soyturk wrote:
> Next program makes a slurpy tailcall, and it causes a memory leak for me.
Confirmed. Interestingly, the problem looks like a Key PMC somewhere gets
garbage collected inappropriately.
I tried various tricks to mark the call_
# New Ticket Created by "Mehmet Yavuz Selim Soyturk"
# Please include the string: [perl #42790]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42790 >
Next program makes a slurpy tailcall, and it causes a memory leak for me
