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
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
