Re: Different Invocation Schemes Make No Sense

2007-07-13 Thread Will Coleda
If I try this against r19833, I get: Invoking Parrot to generate runtime/parrot/include/config.fpmc -- cross your fingers ./miniparrot config_lib.pasm > runtime/parrot/include/config.fpmc make: *** [runtime/parrot/include/config.fpmc] Error 138 even with a realclean. $ sw_vers ProductName:

Re: Different Invocation Schemes Make No Sense

2007-07-09 Thread chromatic
On Monday 09 July 2007 02:49:03 Nuno 'smash' Carvalho wrote: > I saw your sentinel patch but didn't apply it yet. > Is this related to you sentnel patch? I can re-test this after appling it. Here's a better version. I suspect it's not very portable. It probably needs to fix up page alignment,

Re: Different Invocation Schemes Make No Sense

2007-07-09 Thread Nuno 'smash' Carvalho
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/transNOK 19/22 # Failed test (t/op/trans.t at li

Different Invocation Schemes Make No Sense

2007-07-07 Thread chromatic
I'm tracking down potential memory corruption with my sentinel patch. Here's something really weird: $ prove t/op/trans.t t/op/transNOK 19/22 # Failed test (t/op/trans.t at line 511) # Exited with error code: 134 # Received: # Aborte