-
Notifications
You must be signed in to change notification settings - Fork 59
Open
Labels
bugSomething isn't workingSomething isn't working
Description
After issuing make
using 02a7451, SBCL 1.5.6 crashes (see below). This issue does not occur with SBCL 1.5.5 though.
Zapping info...
CORRUPTION WARNING in SBCL pid 25396(tid 0xb7f05c0):
Memory fault at 0x0 (pc=0x100001a697, fp=0x732b08, sp=0x732b00) tid 0xb7f05c0
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
While evaluating the form starting at line 14, column 0
of #P"/Users/jbellorivas/rigetti/qvm/build-app.lisp":
Unhandled SB-SYS:MEMORY-FAULT-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING
{10005404C3}>:
CORRUPTION WARNING in SBCL pid 25396(tid 0xb7f05c0):
Memory fault at 0x0 (pc=0x100001f917, fp=0x731a30, sp=0x731a28) tid 0xb7f05c0
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
#<error printing a SB-SYS:MEMORY-FAULT-ERROR: #<SB-SYS:MEMORY-FAULT-ERROR {1009606DA3}>>
Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10005404C3}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SB-SYS:MEMORY-FAULT-ERROR {1009601D63}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SB-SYS:MEMORY-FAULT-ERROR {1009601D63}>)
2: (INVOKE-DEBUGGER #<SB-SYS:MEMORY-FAULT-ERROR {1009601D63}>)
3: (ERROR SB-SYS:MEMORY-FAULT-ERROR :ADDRESS 0)
4: (SB-SYS:MEMORY-FAULT-ERROR #<unused argument> #.(SB-SYS:INT-SAP #X00000000))
5: ("foreign function: call_into_lisp")
6: ("foreign function: funcall2")
7: ("foreign function: handle_memory_fault_emulation_trap")
8: ("foreign function: signal_emulation_wrapper")
unhandled condition in --disable-debugger mode, quitting
CORRUPTION WARNING in SBCL pid 25396(tid 0xb7f05c0):
Memory fault at 0x0 (pc=0x1000018027, fp=0x731fc0, sp=0x731fb8) tid 0xb7f05c0
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working