tt1931-nci-parameters-deprecation branch ready for testing

Peter Lobsinger plobsing at gmail.com
Wed Apr 27 15:48:04 UTC 2011


On Wed, Apr 27, 2011 at 8:15 AM, James E Keenan <jkeen at verizon.net> wrote:
>
> On Apr 26, 2011, at 7:34 PM, James E Keenan wrote:
>
>>
>>
>> I still have to see whether the problems on Darwin/PPC pasted last night
>> persist.
>>
>
> On Darwin/PPC, when I compile with cc=gcc ld=g++ link=g++, the build
> completes and all tests PASS:
>
> http://smolder.parrot.org/app/projects/report_details/15600
>
> However, when I change the above to cc=g++, the build fails here:
>
> ./parrot-nqp --target=pir
> --output=compilers/opsc/gen/Ops/Compiler/Grammar.pir
> compilers/opsc/src/Ops/Compiler/Grammar.pm
> src/gc/gc_gms.c:1231: failed assertion '!PObj_on_free_list_TEST(pmc) ||
> !"Resurrecting of dead objects is not supported"'
> make: *** [compilers/opsc/gen/Ops/Compiler/Grammar.pir] Abort trap
> ./parrot-nqp --target=pir
> --output=compilers/opsc/gen/Ops/Compiler/Grammar.pir
> compilers/opsc/src/Ops/Compiler/Grammar.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/Emitter.pir
> compilers/opsc/src/Ops/Emitter.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/Trans.pir
> compilers/opsc/src/Ops/Trans.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/Trans/C.pir
> compilers/opsc/src/Ops/Trans/C.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/Op.pir
> compilers/opsc/src/Ops/Op.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/OpLib.pir
>  compilers/opsc/src/Ops/OpLib.pm
> ./parrot-nqp --target=pir --output=compilers/opsc/gen/Ops/File.pir
> compilers/opsc/src/Ops/File.pm
> src/gc/gc_gms.c:1231: failed assertion '!PObj_on_free_list_TEST(pmc) ||
> !"Resurrecting of dead objects is not supported"'
> make: *** [compilers/opsc/gen/Ops/File.pir] Abort trap
>
>
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>

Can you provide a C backtrace for these assertion violations? These
are both GC-related problems on a branch that shouldn't affect GC much
if any, making me suspect we may have simply uncovered GC problems
elsewhere.


More information about the parrot-dev mailing list