-
-
Notifications
You must be signed in to change notification settings - Fork 57
Program terminated with signal SIGILL, Illegal instruction #440
Comments
Hrm. This one's new. Try running with the command |
Please find attached the log bcml-debug.zip Is there a version of bcml with debug symbols so we can have a readable stack back trace? |
With an error like that it's probably not traceable, even with debugging. But it's possible to try by setting up to build from source. |
Error is happening between the log lines No idea what could be causing the error there, as all 10-12 lines of bcml code that are between those two log lines are reused code that has been run successfully at least twice already, before you get to the stage of installation that you're at. I suspect it might be something with the multiprocessing pool, as I can't imagine any of the pure python failing that harshly, but I could be wrong. Can't help much more than that, as I'm purely on Windows and can't reproduce the error. |
@NiceneNerd wrote
Why do you think it is not tracable when we get a readable stack backtrace? Do we have a container build environment like other projects do? I don't want to pollute my production system with the build environment installation. |
I get what i believe to be a SIGLL error right about here, if this helps. also don't know why. Merging 1342 SARC files... |
Going to go ahead and close this as a duplicate of #436 |
Loading BOTW Mod Pack failes with SIGILL.
Please let me know if you need further information.
The text was updated successfully, but these errors were encountered: