[perl #44363] [PATCH] -D80 + bad luck = segfault

2008-03-16 Thread James Keenan via RT
Bram, chromatic: There's been no activity in this thread since last August. Can you give us an update on the issues at hand? Thank you very much. kid51

Re: [perl #44363] [PATCH] -D80 + bad luck = segfault

2008-03-16 Thread Bram Geron
James Keenan via RT wrote: There's been no activity in this thread since last August. Can you give us an update on the issues at hand? I haven't got the problem in a while, so I think it's disappeared. I haven't watched the list closely enough to say why, but I guess it's over. Cheers, Bram

Re: [perl #44363] [PATCH] -D80 + bad luck = segfault

2007-08-05 Thread Bram Geron
chromatic via RT wrote: On Friday 03 August 2007 05:15:33 Bram Geron wrote: At Parrot exit, we force-destroy all PObjs. It can happen that a context is destroyed after its sub is destroyed. Usually that's not a problem, but if you run with -D80 (show when contexts are destroyed, and print

Re: [perl #44363] [PATCH] -D80 + bad luck = segfault

2007-08-04 Thread chromatic
On Friday 03 August 2007 05:15:33 Bram Geron wrote: At Parrot exit, we force-destroy all PObjs. It can happen that a context is destroyed after its sub is destroyed. Usually that's not a problem, but if you run with -D80 (show when contexts are destroyed, and print out the name of the sub) we

[perl #44363] [PATCH] -D80 + bad luck = segfault

2007-08-03 Thread via RT
# New Ticket Created by Bram Geron # Please include the string: [perl #44363] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44363 At Parrot exit, we force-destroy all PObjs. It can happen that a context is destroyed