Try "import sage.all" first. On Monday, January 17, 2022 at 1:13:38 PM UTC-8 marc....@gmail.com wrote:
> While many things work in the binary macOS app for Arm CPU, I discovered > by accident that the following produces a segfault: > > sage: M = Manifold() > > In fact, even trying to import manifold from sage.manifolds segfaults. > This does not happen on the Intel version of the app built from the same > branch of the repository. > > I have not been able to run a debugger on sage at all. Of course > cysignals cannot produce a backtrace on macOS. With lldb -p I get an error > saying that lldb is not allowed to attach to the process and referring me > to non-existent messages in system.log for explanations. Running the > debugserver directly produces: > error: failed to attach process 6619: unable to start the exception thread > > This occurs even if I run sage directly in the repo after the build > finishes - it does not have anything to do with the app. (And the debugger > similarly refuses to attach to the process.) I tried to run the debugger > as root and I also tried adding debugger entitlements and resigning the > app. Neither make it possible for me to use lldb on sage itself. > > I am able to start the sage python3 in lldb. If I knew how to import the > Manifold class from python I might be able to get somewhere. But if I run > >>> from sage.manifolds import manifold > I get a python exception whose traceback ends with: > File "sage/structure/category_object.pyx", line 60, in init > sage.structure.category_object > (build/cythonized/sage/structure/category_object.c:9914) > ImportError: cannot import name Category > > - Marc > > On Saturday, January 15, 2022 at 4:30:08 PM UTC-6 Marc Culler wrote: > >> Hi Matthias, >> >> I have posted binary releases for 9.5.rc1 on macOS with Intel or Arm CPUs >> at https://github.com/3-manifolds/Sage_macOS/releases/tag/v1.3-rc1. >> There are two separate disk images. You may recall that I do not use >> Homebrew or Conda, but I did have to use an experimental binary release of >> gfortran for M1 since I was not able to build the gfortran spkg. >> >> - Marc >> >> On Saturday, January 15, 2022 at 3:01:14 PM UTC-6 matthia...@gmail.com >> wrote: >> > Based on the runs on GH Actions, I have updated the summary of platform >>> support in https://wiki.sagemath.org/ReleaseTours/sage-9.5#Sources >>> >>> TL;DR: It's all good now on all platforms tested on GH Actions, >>> including Cygwin. >>> But I would urge that 9.5 still merge the positively reviews tickets >>> marked "critical"/"blocker", such as >>> https://trac.sagemath.org/ticket/29285 (which fixes the build in the >>> presence of pyenv). >>> Also *note we have absolutely no automatic testing for the Apple >>> Silicon (M1) platform.* So it would be good if users/developers who >>> have access to this platform test the release candidate. >>> >>> >>> >>> On Friday, January 14, 2022 at 8:14:13 AM UTC-8 Matthias Köppe wrote: >>> >>>> On Thursday, January 13, 2022 at 3:22:03 PM UTC-8 Volker Braun wrote: >>>> >>>>> As always, you can get the latest beta version from the "develop" git >>>>> branch. Alternatively, the self-contained source tarball is at >>>>> http://www.sagemath.org/download-latest.html >>>>> >>>>> 3da1b22c25 (HEAD -> develop, tag: 9.5.rc1, trac/develop) Updated >>>>> SageMath version to 9.5.rc1 >>>>> >>>> >>>> Thanks for the new rc. Tests are running at >>>> https://github.com/sagemath/sage/actions/runs/1690315877 (Linux, >>>> macOS) and https://github.com/sagemath/sage/actions/runs/1690315874 >>>> (Cygwin). >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/a9e30c7a-b245-49b4-a472-8fd4b0431e9fn%40googlegroups.com.
