On Monday 30 June 2008 13:00:37 Will Coleda wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #56484]
> # in the subject line of all future correspondence about this issue.
> # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=56484 >
>
>
> Any time we can produce a segfault, that's bad. CC'ing rt to get a ticket.
>
> On Mon, Jun 30, 2008 at 3:55 PM, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> > Given a regular x86 (GNU/Linux) box, using GCC 4.2.3, should the
> > following produce a working Parrot, using 64-bit ints?
> >
> > perl Configure.pl --intval="long long int" --opcode="long long int"
> >
> > If fails for me on C<make> while building PGE.
> >
> > ../../parrot -o PGE.pbc --output-pbc PGE.pir
> > ../../parrot ../../runtime/parrot/library/PGE/Perl6Grammar.pir
> > --output=PGE/builtins_gen.pir PGE/builtins.pg
> > make[1]: *** [PGE.pbc] Segmentation fault
> > make[1]: *** Deleting file `PGE.pbc'
> >
> > The resulting Parrot is partially usable, though.
> >
> > $ ./parrot examples/pasm/hello.pasm
> > Hello World
Ron, do you get any warning messages during Configure? I see:
Figuring out how to pack() Parrot's types...Configure.pl: Unable to find a
functional packtype for intvalsize.
'q' failed: Invalid type 'q' in pack at config/auto/pack.pm
line 62.
Configure.pl: Unable to find a functional packtype for opcode_t_size.
'q' failed: Invalid type 'q' in pack at config/auto/pack.pm
line 62.
There are also plenty of build warnings, such as:
src/headers.c: In function ‘Parrot_destroy_header_pools’:
src/headers.c:912: warning: cast to pointer from integer of different size
I suspect that fixing those would fix the segfaults.
On my system, miniparrot crashes; can you provide a backtrace?
-- c
