Greetings, I saw your sentinel patch but didn't apply it yet.
On 7/7/07, chromatic <[EMAIL PROTECTED]> wrote:
I'm tracking down potential memory corruption with my sentinel patch. Here's something really weird: $ prove t/op/trans.t t/op/trans....NOK 19/22 # Failed test (t/op/trans.t at line 511) # Exited with error code: 134 # Received: # Aborted (core dumped) $ ./parrot "/home/chromatic/dev/parrot/t/op/trans_19.pasm" Aborted (core dumped) $ parrot t/op/trans_19.pasm ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 ok 15 ok 16 $ ./parrot /home/chromatic/dev/parrot/t/op/trans_19.pasm Aborted (core dumped) $ ./parrot t/op/trans_19.pasm ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 ok 15 ok 16 The relative path always succeeds and the absolute path always fails.
I always get success using both: $ ./parrot t/op/trans_19.pasm ok 1 (...) ok 16 $ ./parrot /home/nrc/SVN/parrot/t/op/trans_19.pasm ok 1 (...) ok 16 $ parrot t/op/trans_19.pasm ok 1 (...) ok 16 $ parrot /home/nrc/SVN/parrot/t/op/trans_19.pasm ok 1 (...) ok 16
I'm digging into this. -- c
Is this related to you sentnel patch? I can re-test this after appling it. Best regards, ./smash
