Segmentation fault: 11 with ruff 0.2.0

[jetli]

when run ruff 0.2.0, it always return an error msg: Segmentation fault: 11, but ruff 0.1.15 is ok.

$ ruff --version
Segmentation fault: 11

OS: macOS 11.7.10
python: 3.8.9 in virtual env

[qarmin]

Can you run it under gdb?

gdb ruff
run --version
bt

[MichaReiser]

@jetli, what shell are you using? Is it ZSH? #9824

[charliermarsh]

How strange. Does running with --no-cache change anything? (I assume not, but worth a try.)

[jetli]

not zsh, just bash. it crashes even with no options.

$ ruff
Segmentation fault: 11

installation log:

Collecting ruff
  Using cached ruff-0.2.0-py3-none-macosx_10_12_x86_64.whl (7.3 MB)
Installing collected packages: ruff
  Attempting uninstall: ruff
    Found existing installation: ruff 0.1.15
    Uninstalling ruff-0.1.15:
      Successfully uninstalled ruff-0.1.15
Successfully installed ruff-0.2.0

[charliermarsh]

Do you know what version of macOS you’re on? Perhaps this is related to our upgrade to use the Apple Silicon runners.

[charliermarsh]

Oh sorry, you said macOS 11 above. I’m guessing there’s something incompatible there.

[zanieb]

Could you share the output of the uname -a command?

[Gankra]

I can reproduce this on my old EOL x64 macbook (macos 11 has been eol for 4 months, but i think this issue can plausibly manifest on 12/13).

The crash stack includes lots of things like ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) which is a pretty clear sign the crash is during the dynamic linking of the executable on load. This is probably a symptom of binaries compiled against the macos 14 sdk (the default for github's new apple silicon runners) being run on an older OS.

[charliermarsh]

@Gankra - Do you think this is an issue for ARM macbooks on macos 11, 12, 13? Or just x86? Or can't say at this point?

[Gankra]

I would expect the issue to happen equally on both platforms, with OS version being the primary issue -- but that's purely a guess, and the only thing I can think to do is to find people with macbooks running those versions to try (I guess you could write some github CI jobs to spawn some of those OSes and try to run the binary?).

I can send you the full crash log but it doesn't obviously indicate what symbol was trying to be loaded (only skimmed it).

[charliermarsh]

@Gankra - FYI, it looks like these binaries work okay on macOS 12 and macOS 13: #9835

[charliermarsh]

Now I'm more tempted not to change this given that macOS 11 is EOL :(