wfpokorny
commented
6 years ago Hi. Some questions / thoughts pop to mind.
I see you moved your version from SDL1.2 to SDL2. I hacked for a day - and failed - at such an update around a year ago. I was making it an option to use either version in my case as a first step. Is your compile configuration also set up to still drop back to SDL1.2? If so, could you try this? If not, does running with -D to turn the SDL2 display off work?
If SDL1.2 or -D on the command line works, are you able to get a core file and then a stack trace ?
Does a compile with all optimizations turned off work?
Expect you know, but use configure options "--enable-debug --enable-profile --disable-optimiz --disable-strip" for the latter two and issue a "ulimit -c unlimited" to get the core file in the shell where you execute lpub3d_trace_cui.
I've no experience with Macs but I see too "macOS High Sierra 10.13.2" was the initial release last December that had the meltdown security fix and there look to be folks on the web saying it introduce illegal instruction crashes especially on some AMD cpus. I'm mostly ignorant here, but do you know if your virtual machine was running on an AMD or Intel CPU? If not might be interesting to run the problem set up on an Intel cpu straight up (no VM) and see what happens. Or dig more than I did and see what if any solutions others found for their 10.13.2 issues.
trevorsandy
Summary
I thought you might be interested to know the console application is returning 'Illegal instruction: 4' at the 'Rendering' stage of image generation on macOS High Sierra. The same code base is building and executing without issue on MacOS 10.12 (Travis-Ci). Furthermore, build and test execution are successful across these other 13 platforms so I believe Apple has changed something in High Sierra that is somehow causing an abend during rendering.
Below you can see details of the build output including abend at build check.
Environment
macOS High Sierra 10.13.2 on VMWare Workstation 12 Pro 12.5.8 build 7098237
Workaround
I was not able to bypass the abend despite adding the
-with-macosx-version-min=10.9flag which is a common remedy for the 'Illegal instruction' return message as it 'usually' indicates that clang has encountered and instruction it does not understand. Likely, an instruction that may have been possible in the past but is no longer tolerated.I also reinstalled x11, boost, sdl3, openexr and ilmbase to be sure these external dependencies were well installed.
Lastly, I tried building the official POV-Ray 'release/v3.8.0' source from GitHub but made even less progress. While the build succeeded the 'make check' test consistently failed with
"Data type or kind does not match"Trying to build 'release/v3.7.1' make even less progress still as I did not get pass the many boost/tr errors that blocked successful compilation.
Suggested Solution
My thinking is either a module within POV-Ray or a dependent library is not compliant with macOS High Sierra. I believe this be quickly traced by someone better aware of the rendering engine than I am.
NOTE: Although the instance of POV-Ray depicted in the logs above is customised, the customization only impacts the virtual front end and console display. I do not believe the source of this behaviour is associated with these layers. It this behaviour is indeed thrown from the core, then could be good to raise it with the POV-Ray team. The full source for this instance povray is available here.
Cheers,