Closed brunoh2015 closed 3 years ago
Thanks for helping us to test the SageMath 9.4 app!
It is not an error that there is no path for your notebook directory in the launcher. You just need to set that before you can launch a notebook.
To figure out where the illegal instruction is we need a crash log. Can you please try running this command in your terminal and see if that produces a crash log?
/Applications/SageMath-9-4.app/Contents/Frameworks/Sage.framework/Versions/9.4/local/bin/python3.9
Also, it would be very helpful to know what CPU chip your macbook has. You can find that by running the following command in your terminal:
sysctl -n machdep.cpu.brand_string
On second thought, I am pretty sure that python won't crash, since you do seem to be getting a launcher window and the launcher is a python script. So, assuming that you get a python prompt, please run this command in the python interpreter:
>>> import sage
no, thanks to you for your precious hard work!
here is what the sysctl -n machdep.cpu.brand_string command line produce Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
the command /Applications/SageMath-9-4.app/Contents/Frameworks/Sage.framework/Versions/9.4/local/bin/python3.9 launch the python interpreter. What is the name of the crash log? I cannot find it in the directory.
The python command
import sage does not produce anything apparently. Just the next python prompt >>>.
By the way, how do I set my notebook directory for Jupyter notebooks that the sage launcher can see?
If I launch the command sage -n jupyter the Jupiter server launches, but note the sage math Kernel I got two errors 1/ Error loading server extension jupyterlab and then 2/Unhandled SIGILL: An illegal instruction occurred. This probably occurred because a compiled module has a bug in it and is not properly wrapped with sig_on(), sig_off(). Python will now terminate.
On 14 Jul 2021, at 19:59, Marc Culler @.***> wrote:
Thanks for helping us to test the SageMath 9.4 app!
It is not an error that there is no path for your notebook directory in the launcher. You just need to set that before you can launch a notebook.
To figure out where the illegal instruction is we need a crash log. Can you please try running this command in your terminal and see if that produces a crash log?
/Applications/SageMath-9-4.app/Contents/Frameworks/Sage.framework/Versions/9.4/local/bin/python3.9
Also, it would be very helpful to know what CPU chip your macbook has. You can find that by running the following command in your terminal: sysctl -n machdep.cpu.brand_string
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/3-manifolds/Sage_macOS/issues/19#issuecomment-880096268, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIU5S3SWPIJVEQ66HVTQZTTXXF6TANCNFSM5AL5PWIA.
Your CPU is new enough to support the SSE2 and AVX2 instruction sets. So that is not the issue.
The crash report usually pops up as a window. But you might have to open the Console.app and view the crash reports shown in it.
To set your directory for storing sage notebooks, start the app and click the radio button labeled "Jupyter notebook from folder:". Then click the button labeled "Select ...". That will open a file chooser. You should not be allowed to launch the app until you have selected a directory. A dialog window should pop up asking you to choose a folder.
This app uses Jupyter notebooks, but it does not use JupyterLab. So I think your problem may be caused by other software installed on your system which somehow is getting accessed by the SageMath app. The crash may not be a true illegal instruction. It might be related to a signed and notarized app attempting to loading a library that is not signed.
Please report what you see when you run the command
ls -l /usr/local/share/jupyter/kernels
That would be a good place to start.
0/ Thank you for your clear explanations
1/ here is the beginning of the crash report Process: python3.9 [7176] Path: /Applications/SageMath-9-4.app/Contents/Frameworks/Sage.framework/Versions/9.4/local/bin/python3.9 Identifier: python3.9 Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [7175] Responsible: Terminal [7148] User ID: 501
Date/Time: 2021-07-15 11:12:26.757 +0200 OS Version: macOS 11.4 (20F71) Report Version: 12 Anonymous UUID: FC82D41D-2EBE-AEA1-007E-A84E14A1A7EB
Sleep/Wake UUID: 867A66AD-395F-45DE-A761-8BEBD0CF79D2
Time Awake Since Boot: 24000 seconds Time Since Wake: 190 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff2056792e __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff205965bd pthread_kill + 263 2 libsystem_c.dylib 0x00007fff2047abe5 raise + 26 3 signals.cpython-39-darwin.so 0x000000010417f0c3 0x104176000 + 37059 4 signals.cpython-39-darwin.so 0x000000010417ef22 0x104176000 + 36642 5 libsystem_platform.dylib 0x00007fff205dbd7d _sigtramp + 29 6 ??? 000000000000000000 0 + 0 7 libgmp.10.dylib 0x000000010333258b 0x1032c6000 + 443787
Thread 1: 0 libsystem_kernel.dylib 0x00007fff20563cde __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff20596e49 _pthread_cond_wait + 1298 2 libpython3.9.dylib 0x00000001012dbe52 PyThread_acquire_lock_timed + 514 3 libpython3.9.dylib 0x000000010132c10f 0x101158000 + 1917199 4 libpython3.9.dylib 0x000000010132be5c 0x101158000 + 1916508 5 libpython3.9.dylib 0x00000001011a8ca3 0x101158000 + 330915 6 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 7 libpython3.9.dylib 0x0000000101285ef1 _PyEval_EvalFrameDefault + 27073 8 libpython3.9.dylib 0x000000010128a063 0x101158000 + 1253475 9 libpython3.9.dylib 0x00000001011a0430 _PyFunction_Vectorcall + 256 10 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 11 libpython3.9.dylib 0x0000000101285ef1 _PyEval_EvalFrameDefault + 27073 12 libpython3.9.dylib 0x000000010128a063 0x101158000 + 1253475 13 libpython3.9.dylib 0x00000001011a0430 _PyFunction_Vectorcall + 256 14 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 15 libpython3.9.dylib 0x0000000101285ef1 _PyEval_EvalFrameDefault + 27073 16 libpython3.9.dylib 0x00000001011a0525 0x101158000 + 296229 17 libpython3.9.dylib 0x000000010128621a _PyEval_EvalFrameDefault + 27882 18 libpython3.9.dylib 0x000000010128a063 0x101158000 + 1253475 19 libpython3.9.dylib 0x00000001011a0430 _PyFunction_Vectorcall + 256 20 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 21 libpython3.9.dylib 0x0000000101285fad _PyEval_EvalFrameDefault + 27261 22 libpython3.9.dylib 0x00000001011a0525 0x101158000 + 296229 23 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 24 libpython3.9.dylib 0x0000000101285ef1 _PyEval_EvalFrameDefault + 27073 25 libpython3.9.dylib 0x00000001011a0525 0x101158000 + 296229 26 libpython3.9.dylib 0x00000001012890ab 0x101158000 + 1249451 27 libpython3.9.dylib 0x0000000101285ef1 _PyEval_EvalFrameDefault + 27073 28 libpython3.9.dylib 0x00000001011a0525 0x101158000 + 296229 29 libpython3.9.dylib 0x00000001011a2982 0x101158000 + 305538 30 libpython3.9.dylib 0x000000010132cb56 0x101158000 + 1919830 31 libpython3.9.dylib 0x00000001012dba59 0x101158000 + 1587801 32 libsystem_pthread.dylib 0x00007fff205968fc _pthread_start + 224 33 libsystem_pthread.dylib 0x00007fff20592443 thread_start + 15
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x000000010e04ce00 rcx: 0x000000010418f3d8 rdx: 0x0000000000000000 rdi: 0x0000000000000103 rsi: 0x0000000000000004 rbp: 0x000000010418f400 rsp: 0x000000010418f3d8 r8: 0x00007fff8088e068 r9: 0x0000000000000000 r10: 0x000000010e04ce00 r11: 0x0000000000000246 r12: 0x0000000000000103 r13: 0x00007ffeeeab3f10 r14: 0x0000000000000004 r15: 0x0000000000000016 rip: 0x00007fff2056792e rfl: 0x0000000000000246 cr2: 0x000000010418ede0
2/ here is what I see when I launch the command ls -l /usr/local/share/jupyter
total 0 drwxr-xr-x 3 root wheel 96 Jun 24 23:12 kernels drwxr-xr-x 5 root wheel 160 Jul 13 22:45 lab
On 14 Jul 2021, at 22:54, Marc Culler @.***> wrote:
Your CPU is new enough to support the SSE2 and AVX2 instruction sets. So that is not the issue.
The crash report usually pops up as a window. But you might have to open the Console.app and view the crash reports shown in it.
To set your directory for storing sage notebooks, start the app and click the radio button labeled "Jupyter notebook from folder:". Then click the button labeled "Select ...". That will open a file chooser. You should not be allowed to launch the app until you have selected a directory. A dialog window should pop up asking you to choose a folder.
This app uses Jupyter notebooks, but it does not use JupyterLab. So I think your problem may be caused by other software installed on your system which somehow is getting accessed by the SageMath app. The crash may not be a true illegal instruction. It might be related to a signed and notarized app attempting to loading a library that is not signed.
Please report what you see when you run the command ls -l /usr/local/share/jupyter That would be a good place to start.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/3-manifolds/Sage_macOS/issues/19#issuecomment-880202475, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIU5SZTMVMZA2FHDVHKZG3TXX2P3ANCNFSM5AL5PWIA.
Thanks!
So the crash occurs in libgmp at offset 443787 = 0x6c58b. The instruction at that address is a no-op (nopl (%rax,%rax)). That is certainly not an illegal instruction. I believe that the SIGILL signal is actually being generated by the gatekeeper in the function call that precedes that no-op and it is doing that because the signed and notarized SageMath app is trying to access something it is not allowed to access. The illegal access appears to be something related to JupyterLab. You have JupyterLab installed on your system, as evidenced by the existence of the directory /usr/local/share/jupyter/lab. I suspect that if you removed that directory, or temporarily moved it e.g. by running
sudo mv /usr/local/share/jupyter/lab /usr/local/share_jupyter_lab
then you would find that the app works. If my suspicion is correct this is not a solution, but would provide some useful information.
well, unfortunately it is not sufficient the same problem appeared
so i uninstall 9.4-beta1 and install Sagemath 9.3
/usr/local/bin/sage: line 20: 2989 Illegal instruction: 4 $SYMLINK/local/bin/sage $@
and if I use sage in Jupyter notebook, the beginning of crash report is
Crashed Thread: 0 ZMQbg/1 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Thread 0 Crashed:: ZMQbg/1 Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff2042992e __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff204585bd pthread_kill + 263 2 libsystem_c.dylib 0x00007fff2033cbe5 raise + 26 3 signals.cpython-39-darwin.so 0x000000010c73b0d3 0x10c732000 + 37075 4 signals.cpython-39-darwin.so 0x000000010c73aeec 0x10c732000 + 36588 5 libsystem_platform.dylib 0x00007fff2049dd7d _sigtramp + 29 6 ??? 000000000000000000 0 + 0 7 libgmp.10.dylib 0x000000010b80faab 0x10b7a2000 + 449195
Thread 1: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 libzmq.5.dylib 0x000000010b172f65 0x10b15d000 + 89957 2 libzmq.5.dylib 0x000000010b19f8ae 0x10b15d000 + 272558 3 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 4 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
On 15 Jul 2021, at 16:22, Marc Culler @.***> wrote:
Thanks!
So the crash occurs in libgmp at offset 443787 = 0x6c58b. The instruction at that address is a no-op (nopl (%rax,%rax)). That is certainly not an illegal instruction. I believe that the SIGILL signal is actually being generated by the gatekeeper in the function call that precedes that no-op and it is doing that because the signed and notarized SageMath app is trying to access something it is not allowed to access. The illegal access appears to be something related to JupyterLab. You have JupyterLab installed on your system, as evidenced by the existence of the directory /usr/local/share/jupyter/lab. I suspect that if you removed that directory, or temporarily moved it e.g. by running sudo mv /usr/local/share/jupyter/lab /usr/local/share_jupyter_lab then you would find that the app works. If my suspicion is correct this is not a solution, but would provide some useful information.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/3-manifolds/Sage_macOS/issues/19#issuecomment-880736775, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIU5SYQIYY5ZX7HBF4F3ITTX3VLXANCNFSM5AL5PWIA.
That appears to be the same crash, also in libgmp.10.dylib.
Could you also try removing or temporarily moving your ~/.sage directory?
Also, it would be helpful to see the part of the crash log that shows where libgmp.10.dylib is being found on your system.
Do you still get the error message that mentions JupyterLab?
1/ no more error message mentioning JupyterLab
2/ I removed my ~/.sage directory. No change. Same error message
3/ Here is the complete log
Crashed Thread: 0 ZMQbg/1 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Thread 0 Crashed:: ZMQbg/1 Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff2042992e __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff204585bd pthread_kill + 263 2 libsystem_c.dylib 0x00007fff2033cbe5 raise + 26 3 signals.cpython-39-darwin.so 0x0000000107e970d3 0x107e8e000 + 37075 4 signals.cpython-39-darwin.so 0x0000000107e96eec 0x107e8e000 + 36588 5 libsystem_platform.dylib 0x00007fff2049dd7d _sigtramp + 29 6 ??? 000000000000000000 0 + 0 7 libgmp.10.dylib 0x0000000106f6baab 0x106efe000 + 449195
Thread 1: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 libzmq.5.dylib 0x00000001068cef65 0x1068b9000 + 89957 2 libzmq.5.dylib 0x00000001068fb8ae 0x1068b9000 + 272558 3 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 4 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 2: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 libzmq.5.dylib 0x00000001068cef65 0x1068b9000 + 89957 2 libzmq.5.dylib 0x00000001068fb8ae 0x1068b9000 + 272558 3 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 4 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 3: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 select.cpython-39-darwin.so 0x00000001051573d7 0x105151000 + 25559 2 libpython3.9.dylib 0x0000000104a626e2 0x104a0c000 + 354018 3 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 4 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 5 libpython3.9.dylib 0x0000000104b3f4ff 0x104a0c000 + 1258751 6 libpython3.9.dylib 0x0000000104a5a0cb _PyFunction_Vectorcall + 251 7 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 8 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 9 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 10 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 11 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 12 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 13 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 14 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 15 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 16 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 17 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 18 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 19 libpython3.9.dylib 0x0000000104a5c55b 0x104a0c000 + 329051 20 libpython3.9.dylib 0x0000000104b3b797 _PyEval_EvalFrameDefault + 28839 21 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 22 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 23 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 24 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 25 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 26 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 27 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 28 libpython3.9.dylib 0x0000000104a5c55b 0x104a0c000 + 329051 29 libpython3.9.dylib 0x0000000104bd9956 0x104a0c000 + 1890646 30 libpython3.9.dylib 0x0000000104b8ca19 0x104a0c000 + 1575449 31 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 32 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 4:: ZMQbg/3 0 libsystem_kernel.dylib 0x00007fff204299ca poll + 10 1 libzmq.5.dylib 0x0000000106908cef zmq_poll + 511 2 libzmq.5.dylib 0x00000001068dea36 0x1068b9000 + 154166 3 _device.cpython-39-darwin.so 0x00000001069de6d0 0x1069d9000 + 22224 4 _device.cpython-39-darwin.so 0x00000001069dd54f 0x1069d9000 + 17743 5 libpython3.9.dylib 0x0000000104a59917 _PyObject_MakeTpCall + 375 6 libpython3.9.dylib 0x0000000104b3e727 0x104a0c000 + 1255207 7 libpython3.9.dylib 0x0000000104b3b46e _PyEval_EvalFrameDefault + 28030 8 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 9 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 10 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 11 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 12 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 13 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 14 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 15 libpython3.9.dylib 0x0000000104a5c55b 0x104a0c000 + 329051 16 libpython3.9.dylib 0x0000000104bd9956 0x104a0c000 + 1890646 17 libpython3.9.dylib 0x0000000104b8ca19 0x104a0c000 + 1575449 18 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 19 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 5: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 libzmq.5.dylib 0x00000001068cef65 0x1068b9000 + 89957 2 libzmq.5.dylib 0x00000001068fb8ae 0x1068b9000 + 272558 3 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 4 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 6: 0 libsystem_kernel.dylib 0x00007fff20427c4a kevent + 10 1 libzmq.5.dylib 0x00000001068cef65 0x1068b9000 + 89957 2 libzmq.5.dylib 0x00000001068fb8ae 0x1068b9000 + 272558 3 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 4 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 7: 0 libsystem_kernel.dylib 0x00007fff20425cde __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff20458e49 _pthread_cond_wait + 1298 2 libpython3.9.dylib 0x0000000104b8cdb5 PyThread_acquire_lock_timed + 421 3 libpython3.9.dylib 0x0000000104bd8def 0x104a0c000 + 1887727 4 libpython3.9.dylib 0x0000000104bd8b3c 0x104a0c000 + 1887036 5 libpython3.9.dylib 0x0000000104a625da 0x104a0c000 + 353754 6 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 7 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 8 libpython3.9.dylib 0x0000000104b3f4ff 0x104a0c000 + 1258751 9 libpython3.9.dylib 0x0000000104a5a0cb _PyFunction_Vectorcall + 251 10 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 11 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 12 libpython3.9.dylib 0x0000000104b3f4ff 0x104a0c000 + 1258751 13 libpython3.9.dylib 0x0000000104a5a0cb _PyFunction_Vectorcall + 251 14 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 15 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 16 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 17 libpython3.9.dylib 0x0000000104b3b797 _PyEval_EvalFrameDefault + 28839 18 libpython3.9.dylib 0x0000000104b3f4ff 0x104a0c000 + 1258751 19 libpython3.9.dylib 0x0000000104a5a0cb _PyFunction_Vectorcall + 251 20 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 21 libpython3.9.dylib 0x0000000104b3b510 _PyEval_EvalFrameDefault + 28192 22 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 23 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 24 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 25 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 26 libpython3.9.dylib 0x0000000104b3e6f3 0x104a0c000 + 1255155 27 libpython3.9.dylib 0x0000000104b3b44e _PyEval_EvalFrameDefault + 27998 28 libpython3.9.dylib 0x0000000104a5a205 0x104a0c000 + 320005 29 libpython3.9.dylib 0x0000000104a5c55b 0x104a0c000 + 329051 30 libpython3.9.dylib 0x0000000104bd9956 0x104a0c000 + 1890646 31 libpython3.9.dylib 0x0000000104b8ca19 0x104a0c000 + 1575449 32 libsystem_pthread.dylib 0x00007fff204588fc _pthread_start + 224 33 libsystem_pthread.dylib 0x00007fff20454443 thread_start + 15
Thread 8: 0 libsystem_pthread.dylib 0x00007fff20454420 start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000112585e00 rcx: 0x0000000107ea73c8 rdx: 0x0000000000000000 rdi: 0x0000000000000103 rsi: 0x0000000000000004 rbp: 0x0000000107ea73f0 rsp: 0x0000000107ea73c8 r8: 0x00007fff80750068 r9: 0x0000000000000000 r10: 0x0000000112585e00 r11: 0x0000000000000246 r12: 0x0000000000000103 r13: 0x00007ffeeb1fb800 r14: 0x0000000000000004 r15: 0x0000000000000016 rip: 0x00007fff2042992e rfl: 0x0000000000000246 cr2: 0x0000000107ea6dd0
Logical CPU: 0 Error Code: 0x02000148 Trap Number: 133
Thread 0 instruction stream: 47 20 c4 62 bb f6 4e f0-f3 4c 0f 38 f6 57 28 66 G .b..N..L.8.W(f 4d 0f 38 f6 c3 4c 89 57-28 f3 4c 0f 38 f6 47 30 M.8..L.W(.L.8.G0 c4 62 ab f6 5e f8 4c 89-47 30 48 8d 7f 40 66 4d .@.M 0f 38 f6 d1 c4 62 bb f6-0e e9 39 ff ff ff 48 8d .8...b....9...H. 7f c0 4c 8b 5e e8 48 8b-56 f0 c4 42 fb f7 d3 c4 ..L.^.H.V..B.... 42 fa f7 db 49 21 d3 c4-62 bb f6 ca 49 8d 14 52 B...I!..b...I..R [66]4d 0f 38 f6 c3 f3 4c-0f 38 f6 47 38 c4 62 ab fM.8...L.8.G8.b. <== f6 5e f8 4c 89 47 38 66-4d 0f 38 f6 d1 c4 62 e3 .^.L.G8fM.8...b. f6 0e f3 4c 0f 38 f6 57-40 66 49 0f 38 f6 db 4c ...@.I.8..L 89 57 40 f3 48 0f 38 f6-5f 48 f3 4c 0f 38 f6 c9 .@.***H.8._H.L.8.. 49 11 c9 4c 89 4f 50 4c-8b 4e f0 48 8b 56 f8 c4 I..L.OPL.N.H.V.. 42 fb f7 c1 c4 42 fa f7-c9 49 21 d1 c4 62 ab f6 B....B...I!..b..
Thread 0 last branch register state not available.
Binary Images:
0x1049fb000 - 0x1049fefff +python3 (0) <353C3350-2970-3C72-A885-219F979F24F4> /var/tmp//python3
0x104a0c000 - 0x104c83fff +libpython3.9.dylib (0) <86451832-18F4-37B4-B6F5-FDA94047BF08> /Applications/SageMath-9-3.app/Contents/Frameworks/Sage.framework/Versions/9.3/local/lib/libpython3.9.dylib
0x104f29000 - 0x104f2cfff +_heapq.cpython-39-darwin.so (0)
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 0 thread_create: 0 thread_set_state: 0
VM Region Summary: ReadOnly portion of Libraries: Total=609.9M resident=0K(0%) swapped_out_or_unallocated=609.9M(100%) Writable regions: Total=235.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=235.9M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= Activity Tracing 256K 1 Dispatch continuations 64.0M 1 Kernel Alloc Once 8K 1 MALLOC 78.1M 46 MALLOC guard page 16K 4 MALLOC_LARGE (reserved) 256K 1 reserved VM address space (unallocated) SQLite page cache 64K 1 STACK GUARD 32K 8 Stack 66.6M 10 Stack Guard 4K 1 VM_ALLOCATE 25.5M 104 DATA 5822K 249 DATA_CONST 6357K 96 DATA_DIRTY 288K 62 LINKEDIT 504.4M 183 OBJC_RO 70.2M 1 OBJC_RW 2480K 2 TEXT 106.1M 244 UNICODE 588K 1 mapped file 36K 1 shared memory 8K 2 =========== ======= ======= TOTAL 930.8M 1019 TOTAL, minus reserved VM space 930.5M 1019
On 15 Jul 2021, at 22:13, Marc Culler @.***> wrote:
That appears to be the same crash, also in libgmp.10.dylib.
Could you also try removing or temporarily moving your ~/.sage directory?
Also, it would be helpful to see the part of the crash log that shows where libgmp.10.dylib is being found on your system.
Do you still get the error message that mentions JupyterLab?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/3-manifolds/Sage_macOS/issues/19#issuecomment-880982776, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIU5S7BTHFJV5E53MRDGTLTX46M7ANCNFSM5AL5PWIA.
Thank you. I can now see that for both 9.3 and 9.4 the crash happens in the function gmp_randinit_mt. Also the 9.3 version has a bit more information which should be helpful. It is clear from looking at the disassembled libraries that in both cases the crash occurs at the same line of gmp_randinit_mt. I will try to locate where the crash is happening in gmp and see what I can learn from looking at the code.
@brunoh2015 reported that the crash still occurs with the 9.4.rc0 prerelease which is compiled with -no-avx2.
Closing this issue and merging with #16.
I am using a MacBook Pro 2015 with OS X Big Sur 11.4
After I installed the beta of sagemath-9.4
1/ there is no path for Jupyter in the launcher 2/ a console version of sage does not work I got this error
Unhandled SIGILL: An illegal instruction occurred. This probably occurred because a compiled module has a bug in it and is not properly wrapped with sig_on(), sig_off(). Python will now terminate.
/usr/local/bin/sage: line 19: 3726 Illegal instruction: 4 $SYMLINK/local/bin/sage $@
What do you suggest?