https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #3 from Richard W.M. Jones <rjones at redhat dot com> --- (Edit comment 2: To be clear, that wasn't the thread where the segfault occurred, which was some golang thread, that was the thread that was unmapping the memory at the same time. Using nodelete avoids this by not actually unmapping the code.)