-
-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Post-mortem] PrimitiveFailed: primitive #primLoadSymbol:module: in TFFIBackend failed #11561
Comments
Hitting this as well. Mac OS ARM64. It's not just a debugger appearing on opening, it also fails when trying to execute a Metacello load, such as:
|
I am also running into this problem. I tracked the problem to LGitLibrary>>#macLibraryName. The array contains two set of quotes around the first entry. This causes the entry to be interpreted in an interesting manner. Instead of a single entry, it is viewed as 9 separate array entries (as though it were a dynamic array.) When FFIMacLibraryFinder concatenates the empty String to a FileReference, it ends up returning the FileSystem Root. This exists, FFIMacLibraryFinder incorrect determines the name of the library to be '/' and the FFI calls fail. Updating #macLibraryName 'resolves' the bad behavior. There seem to be a few issues at play in this issue.
|
I don't know where to submit a patch for #macLibraryName. I can't seem to find the right repo. I did notice that Feenk has patched this method. |
A student in my course with Moose this semester is hitting this bug (there's no Moose Suite for Pharo 11 as far as I know). Did Pharo 10 get this fix? Maybe the "Moose Suite 10 (development)" image is not using it? |
Bug description
When I create and launch a new image of the latest stable Pharo version 10.0 a debugger opens.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The debugger should not appear.
Version information:
Expected development cost
No idea about that. I am of course willing to test a fix.
PharoDebug.log
The text was updated successfully, but these errors were encountered: