https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77405
--- Comment #16 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to John Marino from comment #15) > There's a complete log showing where in the build the SIGBUG occurs but as > far as the assembly code that causes it, I have no idea. If you provide me > some instructions on how, maybe I can get some useful information for you. Run the failed command under gdb. Then you can get backtrace and disassemble the failed function. It will show where the problem is.
