Comment 4 for bug 1710375

If the bisect is right, this should be simple to isolate as it's confined to the C make steps.
Try building prior to that change and save the C compiler/linker invocations from "make" in src/runtime into a file. Then build at that change, similarly saving the C compilation steps.
Try diffing them, or just eyeballing to see what looks suspicious.
In terms of trying to diagnose in 'ldb', you can type "backtrace", but as a first step it would be best to find out how the C code is being built differently.