Opened 17 months ago
Last modified 17 months ago
#72061 new defect
macports-base 2.10.5: port install/upgrade terminated by signal SIGSEGV (Address boundary error)
| Reported by: | nasyxx (Nasy) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.10.5 |
| Keywords: | sequoia arm64 | Cc: | |
| Port: |
Description
I'm not sure what's wrong here. I'm getting the following situation after a recent update.
> sudo port selfupdate ---> Checking for newer releases of MacPorts MacPorts base version 2.10.5 installed, MacPorts base version 2.10.5 available. ---> MacPorts base is already the latest version ---> Updating the ports tree The ports tree has been updated. 16 ports are outdated. Run 'port outdated' for details. To upgrade your installed ports, you should run port upgrade outdated > sudo port upgrade outdated ---> Computing dependencies for openssl3 ---> Fetching archive for openssl3 ---> Attempting to fetch openssl3-3.4.1_0+rfc3779.darwin_24.arm64.tbz2 from https://packages.macports.org/openssl3 fish: Job 1, 'sudo port upgrade outdated' terminated by signal SIGSEGV (Address boundary error)
I tried recompiling the MacPorts-base from the git source, but that didn't help. Do you have any tips on what's going wrong?
Change History (4)
comment:1 follow-up: 3 Changed 17 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 17 months ago by jmroot (Joshua Root)
Or potentially /Library/Logs rather than ~/Library/Logs since it was running as root.
comment:3 Changed 17 months ago by nasyxx (Nasy)
Replying to ryandesign:
Sounds like a crash occurred. If so, macOS should have recorded a crash log in ~/Library/Logs/DiagnosticReports/. Could you attach it?
Thanks! I found sudo crash logs in ~/Library/Logs/D/, but I'm still at a loss.
I tried rebuilding macports from the master branch, and encountered the this problem:
...
Library: callback.dylib
(tcl 8.6)
Stubs:
critcl-3.3.1/critcl_c/tcl8.6/tclDecls.h:
(tclStubsPtr => const TclStubs *tclStubsPtr;)
critcl-3.3.1/critcl_c/tcl8.6/tclPlatDecls.h:
(tclPlatStubsPtr => const TclPlatStubs *tclPlatStubsPtr;)
Package Placed Into: /Users/Nasy/src/macports-base/vendor/vendor-destroot/Users/Nasy/.macports/libexec/macports/lib/tmp/callback
Platform: macosx-aarch64, macosx-arm, macosx-arm64 15.0 and later
Headers Placed Into: /Users/Nasy/src/macports-base/vendor/vendor-destroot/Users/Nasy/.macports/libexec/macports/lib/tmp/critcl_callback
Done
Installed package: /Users/Nasy/src/macports-base/vendor/vendor-destroot/Users/Nasy/.macports/libexec/macports/lib/critcl_callback_tcl8-1.1
Installed headers: /Users/Nasy/src/macports-base/vendor/vendor-destroot/Users/Nasy/.macports/libexec/macports/include/critcl_callback
chmod: /Users/Nasy/src/macports-base/vendor/vendor-destroot/opt/local/libexec/macports/lib/critcl*: No such file or directory
make[1]: *** [.stamp-critcl] Error 1
make: *** [all] Error 1
Now, I think I've roughly guessed that the problem lies in the fact that my /opt/local is actually a soft link to ~/.macports. It's likely that there's an issue with prefixes, where some parts are expanding the soft link to ~/.macports, while others are still retaining /opt/local.
Maybe later, I should try not to soft link the whole macports but just handle the few confs.
And for now, I install a released version from the pkg.
comment:4 Changed 17 months ago by jmroot (Joshua Root)
Can you share the crash log? A segfault is something we would want to fix regardless of whether it's triggered by an unusual configuration.

Sounds like a crash occurred. If so, macOS should have recorded a crash log in ~/Library/Logs/DiagnosticReports/. Could you attach it?