On Wed, 28 May 2008, Andrew Johnson wrote: > tiger% ./parrot -t t/dynoplibs/myops_3.pir > 0 print "neither here\n" > neither here > 2 hcf > Segmentation fault
Welcome to the club of people who've wasted time chasing this particularly silly test. 'hcf' is supposed to stand for 'halt and catch fire'. I gather it was supposed to be funny. The immediate problem is that the test suite doesn't handle all the possible ways that this operation could crash parrot. For example, as happened here, the process might simply hang and need to be killed. Here's an earlier set of postings about just this same problem: http://groups.google.com/group/perl.perl6.internals/browse_thread/thread/73c18b45ff002077 At a minimum, the test should be deleted. More generally, there is no guarantee what the system will actually do when presented with the code int *a, i; a = NULL; i = *a; The actual result you get will depend on the compiler, the optimization level, and the runtime environment. -- Andy Dougherty [EMAIL PROTECTED]
