On Sat, Sep 15, 2001 at 04:44:47PM +0100, Simon Cozens wrote: > > And segfaults here: > > (gdb) run test.pbc > Starting program: /var/tmp/parrot/test_prog test.pbc > > Program received signal SIGSEGV, Segmentation fault. > 0x120007388 in read_constants_table (program_code=0x11ffffb48) at bytecode.c:66 > 66 IV len = GRAB_IV(program_code); > (gdb) quit > > Don't know why. :( [Apologies if this is out of date -- I'm currently massively behind on perl6-internals] If this is with 64 bit IVs, this is the problem I hit a while back -- we're reading in 32 bit quantities from disc, but 64 bits at a time, so everything goes completely pear shaped. I posted a couple of bodge fixes from this, but I haven't done much in the past couple of days... do we want to use a 32 bit type for reading in bytecode or convert the 32 bit on-disc format into a 64 bit format in memory before reading it on a platform with 64 bit IVs? Cheers, Phil -- Philip Kendall <[EMAIL PROTECTED]> http://www.srcf.ucam.org/~pak21/
- parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Simon Cozens
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Simon Cozens
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Philip Kendall
- Re: parrot compilation failure in Tru64 Simon Cozens
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- Re: parrot compilation failure in Tru64 Philip Kendall
- Re: parrot compilation failure in Tru64 Sam Tregar
- Re: parrot compilation failure in Tru64 Simon Cozens
- Re: parrot compilation failure in Tru64 Jarkko Hietaniemi
- RE: parrot compilation failure in Tru64 Gibbs Tanton - tgibbs
- Re: parrot compilation failure in Tru64 Philip Kendall