Hi Folks!
I've attached a small pasm file that crashes Parrot. Seems to be a GC issue,
it workes fine if sweepoff is added.
Might be useful for debugging?
cya,
Jens Rieks
#
# small example that crashes parrot
#
set I1, 1
main: bsr print
inc I1
le I1, 100, main
At 8:00 PM +0200 5/23/02, Jens Rieks wrote:
I've attached a small pasm file that crashes Parrot. Seems to be a GC issue,
it workes fine if sweepoff is added.
The GC assumes that the stack entries are always valid, and you
pushed invalid strings onto the stack. (The string register was NULL
Theoretically this shouldn't be done,
In practice you can't assume something like that (at least when using
callee-save calling convention), or do I miss the point?
but I put in a patch to the GC to double check, just in case.
Fine, tanks :)
cya,
Jens Rieks
At 8:55 PM +0200 5/23/02, Jens Rieks wrote:
Theoretically this shouldn't be done,
In practice you can't assume something like that (at least when using
callee-save calling convention), or do I miss the point?
Nope, you didn't miss the point. The GC assumes that the register
frames might be
