# New Ticket Created by chromatic
# Please include the string: [perl #39973]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=39973 >
With a fresh checkout, I'm seeing a weird error:
(gdb) run
Starting program: /home/chromatic/dev/parrot/parrot
[Thread debugging using libthread_db enabled]
[New Thread 805414656 (LWP 8662)]
Parrot VM: PANIC: Out of mem!
C file src/memory.c, line 95
Parrot file (not available), line (not available)
We highly suggest you notify the Parrot team if you have not been working on
Parrot. Use parrotbug (located in parrot's root directory) or send an
e-mail to [EMAIL PROTECTED]
Include the entire text of this error message and the text of the script that
generated the error. If you've made any modifications to Parrot, please
describe them as well.
Version : 0.4.5-devel
Configured : Tue Jul 25 16:55:45 2006
Architecture: ppc-linux
JIT Capable : Yes
Interp Flags: (no interpreter)
Exceptions : (missing from core)
Dumping Core...
Program received signal SIGQUIT, Quit.
[Switching to Thread 805414656 (LWP 8662)]
0x0fc26fbc in raise () from /lib/libpthread.so.0
(gdb) bt
#0 0x0fc26fbc in raise () from /lib/libpthread.so.0
#1 0x0fe053c8 in do_panic (interpreter=Cannot access memory at address 0xb
) at exceptions.c:125
#2 0x0fe1053c in mem__internal_allocate_zeroed (size=1684366396,
file=0xff93790 "src/resources.c", line=63) at memory.c:95
#3 0x0feca1a8 in alloc_new_block (interpreter=0x1001a068, size=1684366372,
pool=0x1001aa20, why=0xff937dc "compact failed") at resources.c:62
#4 0x0feca448 in mem_allocate (interpreter=0x1001a068, size=1684366372,
pool=0x1001aa20) at resources.c:168
#5 0x0fecb36c in Parrot_allocate_string (interpreter=0x1001a068,
str=0x10156f00, size=1684366368) at resources.c:712
#6 0x0fe1cbdc in string_make_direct (interpreter=0x1001a068,
buffer=0x10008a9c, len=1684366368, encoding=0x1003ac70,
charset=0x1003d620, flags=0) at string.c:612
#7 0x0fe1cab0 in string_make (interpreter=0x1001a068, buffer=0x10008a9c,
len=1684366368, charset_name=0xff8bf1c "ascii", flags=0) at string.c:577
#8 0x0fec9b34 in PF_fetch_string (interp=0x1001a068, pf=0x101912d8,
cursor=0x1017d5b4) at pf_items.c:524
#9 0x0fe270a4 in shift_opcode_string (interpreter=0x1001a068, io=0x101912c8)
at pmc_freeze.c:532
It looks like an invalid opcode read. I think this has come up before; I am
on a big-endian arch (PPC).
It's so bad I can't even build anymore.
-- c
