Matthias Hölzl <[EMAIL PROTECTED]> wrote:
> I have appended a backtrace with information about the relevant
> variables. The backtrace seems to support your conclusion that the
> segfault happens during garbage collection.
Yep, thanks for the detailed output.
> 0x080e4169 in pobject_lives (inter
Leopold Toetsch wrote:
Matthias . Hoelzl @ ifi . lmu . de <[EMAIL PROTECTED]> wrote:
Parrot segfaults when executing the appended function.
It's hard to tell, what's the problem. A debugger backtrace with
information about the relevant variables could help.
And: if the code runs with "parro
Matthias . Hoelzl @ ifi . lmu . de <[EMAIL PROTECTED]> wrote:
> Parrot segfaults when executing the appended function.
It's hard to tell, what's the problem. A debugger backtrace with
information about the relevant variables could help.
And: if the code runs with "parrot -G" then it's likely a G
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #32092]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=32092 >
---
osname= linux
osvers= 2.4.21-14.elsmp
arch= i386-linux-thread-multi
cc=
