gmsh problem (segmentation fault) on ARM64 MacOs Sequoia

[fbonaldi]

Output of brew config

HOMEBREW_VERSION: 4.4.19
ORIGIN: https://github.com/Homebrew/brew
HEAD: 23facb219df8615680636ef12103bb3313f44e2a
Last commit: 2 days ago
Branch: stable
Core tap JSON: 29 Jan 18:08 UTC
Core cask tap JSON: 29 Jan 18:08 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.u5J6XQcXjf/org.xquartz:0
HOMEBREW_MAKE_JOBS: 14
Homebrew Ruby: 3.3.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.7/bin/ruby
CPU: 14-core 64-bit arm_brava
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.3-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: 16.2
Rosetta 2: false

Output of brew doctor

Your system is ready to brew.

Description of issue

When running gmsh, I get a segmentation fault error message. I tried to debug it with lldb and the outcome was

Process 20316 launched: '/opt/homebrew/bin/gmsh' (arm64)
Process 20316 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)
    frame #0: 0x000000010054cbf8 gmshonelabGroup::_computeWidths() + 100
gmshonelabGroup::_computeWidths:
->  0x10054cbf8 <+100>: ldr    w8, [x0, #0x8]
    0x10054cbfc <+104>: scvtf  d0, w8
    0x10054cc00 <+108>: fmul   d0, d0, d8
    0x10054cc04 <+112>: fadd   d0, d9, d0
Target 0: (gmsh) stopped.

Downloading and installing the application from the GMSH website gives no problem, but I would like to use the gmsh command from the terminal instead of opening the application.

Relevant casks

gmsh

[cho-m]

This is an upstream issue that is probably fixed by unreleased commit - https://gitlab.onelab.info/gmsh/gmsh/-/commit/3b3f0f7e16430939b345889a9e31b50104d5baf3

Can try patching that in, EDIT: Homebrew/homebrew-core#205934

[cho-m]

New bottle should be available and can be installed with brew reinstall gmsh

[fbonaldi]

Works fine, thank you!

[fbonaldi]

By the way, would it be possible to do something analogous to what is done with ParaView? Installation of GMSH only creates a bin file inside the Homebrew directory, whereas when installing ParaView, an .app file is also created in the /Applications directory and a symlink/alias towards the bin file inside the Contents/MacOS directory of the .app is created under the Homebrew directory (instead of the binary alone).

[gromgit]

Not as such. paraview is a cask, while gmsh is a formula. They're fundamentally different in how they're distributed:

• the ParaView app bundle is provisioned by upstream, while GMSH is built from source by Homebrew
• no formula installation writes anything outside of $HOMEBREW_PREFIX, while casks can be installed anywhere, depending on the upstream installer's code