On 9 November 2015 at 11:06, Peter Maydell <[email protected]> wrote: > On 9 November 2015 at 10:21, Paolo Bonzini <[email protected]> wrote: >> Hmm, so the list is pretty short: > > The good news is that my second bisect conclusively fingered > the culprit for why the bug went away... > >> configure: disable FORTIFY_SOURCE under clang > > ...the bad news is it's because this patch inadvertently makes > all non-fortify-source compiles be no-optimization (and we already > knew the bug didn't repro in an unoptimized build).
Yep, just confirmed that current master with commit b553a0428 reverted displays the bug again. thanks -- PMM
