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 line of inline PIR)
that reproduces the problem for me (using feather, r32150 of parrot
and r124 of partcl)
proc a {} {info vars}
a
inline PIR {
.sub 'foo'
collect
.end
}
a
If run with parrot -G, the segfault goes away. gdb shows that the
location of the segfault hasn't changed even with the much smaller
test, it's still in ascii_compute_hash working on a STRING.
--
Will "Coke" Coleda
