Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test drops me into LDB because of memory fault on MacBook M2&SBCL2.5.0 #2

Open
mirkov opened this issue Jan 1, 2025 · 1 comment
Open

Comments

@mirkov
Copy link

mirkov commented Jan 1, 2025

Test drops me into the SBCL low level debugger because of memory fault. This occurs either in SVD or at start of Spectral Factorization.

CL-USER> (ql:quickload "lla")
CL-USER> (ql:quickload "clunit2")
CL-USER> (asdf:test-system "lla" :verbose t)

PROGRESS:
=========

    TESTS: (Test Suite)

        BLAS-SUITE: (Test Suite)
            GEMM: ....................................................................................................

        LINEAR-ALGEBRA-SUITE: (Test Suite)
            LOGDET: .
            TR: .....
            SVD: ............................................................................................................................................................................................................
            SPECTRAL-FACTORIZATION:

In LDB the output is:

CORRUPTION WARNING in SBCL pid 85869 pthread 0x16dc23000:
Memory fault at 0x0 (pc=0x191311644)
The integrity of this image is possibly compromised.
CORRUPTION WARNING in SBCL pid 85869 pthread 0x16dc23000:
Memory fault at 0x10 (pc=0x102258114)
The integrity of this image is possibly compromised.
... Repeats several times until ...
CORRUPTION WARNING in SBCL pid 85869 pthread 0x16dc23000:
Memory fault at 0x10 (pc=0x102258114)
The integrity of this image is possibly compromised.
fatal error encountered in SBCL pid 85869 pthread 0x16dc23000:
maximum interrupt nesting depth (8) exceeded

Error opening /dev/tty: Device not configured
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>

I don't have the skills to probe what is going on there, but I got the following outputs as well:

ldb> regs
CSP	=	0x1060a3ad8   CFP	=	0x10
ldb> threads
(thread*,pthread,sb-vm:thread,name)
0x106cc0000 0x16dc33000 0x7009a1b9f0 "slynk-worker"
0x1064a0000 0x16dc23000 0x7005720000 "sly-channel-1-mrepl-remote-1"
0x105470000 0x16dc03000 0x7005700830 "slynk-indentation-cache-thread"
0x104430000 0x16dbe3000 0x70057008c0 "reader-thread"
0x104c50000 0x16dbf3000 0x70057006e0 "control-thread"
0x103c20000 0x16dbd3000 0x7005700950 "Slynk Sentinel"
0x103400000 0x16dbc3000 0x70057009e0 "finalizer"
0x102be0000 0x1eb28cf40 0x7005700a70 "main thread"
@moneylobster
Copy link

Seems like a duplicate of #1 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants