Re: [perl #60128] [BUG] GC STRING segfault.

2008-10-29 Thread chromatic
On Monday 27 October 2008 18:18:26 Will Coleda wrote: Attached is a PIR-only file (no tcl required) that triggers the same GC-related segfault (tested in r32210) Fixed in r32229. The problem is that retrieving the STRING value of a String Key returned that STRING directly. Modifying its

Re: [perl #60128] [BUG] GC STRING segfault.

2008-10-27 Thread Will Coleda
On Sun, Oct 26, 2008 at 11:17 AM, Will Coleda [EMAIL PROTECTED] wrote: Turns out setting the conditional breakpoint never fired; left this running overnight, and it eventually came back with the segfault directly. Back to the drawing board. Here is a very small snippet of tcl (with a single

Re: [perl #60128] [BUG] GC STRING segfault.

2008-10-27 Thread Will Coleda
On Mon, Oct 27, 2008 at 9:31 AM, Will Coleda [EMAIL PROTECTED] wrote: On Sun, Oct 26, 2008 at 11:17 AM, Will Coleda [EMAIL PROTECTED] wrote: Here is a very small snippet of tcl SNIP Attached is a PIR-only file (no tcl required) that triggers the same GC-related segfault (tested in r32210) --

[perl #60128] [BUG] GC STRING segfault.

2008-10-26 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #60128] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60128 Trying to track down a segfault that is occurring for me in parrot (triggered by

Re: [perl #60128] [BUG] GC STRING segfault.

2008-10-26 Thread Will Coleda
On Sun, Oct 26, 2008 at 2:00 AM, via RT Will Coleda [EMAIL PROTECTED] wrote: # New Ticket Created by Will Coleda # Please include the string: [perl #60128] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60128