On Sat, Sep 15, 2001 at 04:44:47PM +0100, Simon Cozens wrote: > On Sat, Sep 15, 2001 at 06:44:38PM +0300, Jarkko Hietaniemi wrote: > > The question is why was it wrong after a fresh checkout? (also in Linux) > > No idea. Is make_op_header.pl run? Does op.h contain the #define's? > > > Another observation is that after 'rm op.h; make op.h' the thing > > builds but with some gnashing of the teeth: > > 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. :( I think it's very simply that one cannot deref a void** as a long*, because of memory alignment restrictions (MEM_ALIGNBYTES is 8 in alpha). > Simon -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
- 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