Look for core180920.tar.xz on support for the build logs.
My build logs contain not just the build that had the error, but also many builds before and after. But I have 2 build logs that were getting appended to, I was going back and forth between them (2 different versions of same code, different directories and different branches of the code). Each time I do a new build the build toolwindow (process buffer) is cleared, but the logfiles are appended for each new build.
The timestamp of the core dump is Sep 20 at 16:06
The 2 files in the tarball and build_full.log and build_full2.log.
You can search for when each build started/stopped by doing regular expression search, find in files of these 2 files with this regex:
Starting\(|Stopping\(
So you will find in the search results for build2.log:
294550 1:Starting(Thu Sep 20 16:06:33 2018): ...
294586 1:Stopping(Thu Sep 20 16:06:34 2018): ...
So between lines 294550-294586 is the particular build where the core dump occurred.
You can get a history of builds before that by looking at the timestamps of these 2 files.
From these build logs, it doesn't show my replay of it, but I'm not sure I append the replays to the full build log, but I'm pretty sure I did replay it, you just don't see it in the logs.
There was another build going on during the same time interval in build_full.log, but that build was occurring outside of SE and running in the background, so not every build in these files is done in SE. Currently I have no way of knowing which ones were done in and not in SE - I should probably make a way to distinguish that in the logs for the future.
Another thing that may be important, my process buffer was sshed into a build server at the time I started it, so it had a bash prompt on a different machine where SE was running on.
