Parrot Borking

Hi, I'm having problems with Parrot Segfaulting. What is the most likely line of attack to find out what the cause is ( gdb, parrot debugger, praying, etc.). I'm not a C programmer but I read it fairly well and it is a lot of years since I last used a debugger. My source tree was updated from CVS

[perl #37928] [TODO] build - Parrot::Configure::RunSteps rename

Committed as r10566 & r10567. -J --

Re: Parrot Borking

On Dec 18, 2005, at 10:58, Steve Gunnell wrote: Hi, I'm having problems with Parrot Segfaulting. What is the most likely line of attack to find out what the cause is ( gdb, parrot debugger, praying, etc.). gdb and or valgrind --tool=memcheck Be sure to use always a recent svn c

Strange behaviour of PIR register $P0 vs others

Hi, I get some strange behaviour in the attached code snippet. The problem is with the lines marked with a '*'. If the global 'r' is stored into $P0, and in the second marked line it is called, the output of the print statements furhter below is: Lua_Proto_2_0 2 instead of the expected 1 2

[perl #37924] [TODO] build - load steps by namespace

Committed as r10571. I decided not to use Module::Pluggable at this time as it tries to loading things like the 'hints' modules for all platforms. -J --