https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84428
Peter Rabbitson <ribasushi at leporine dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ribasushi at leporine dot io
--- Comment #3 from Peter Rabbitson <ribasushi at leporine dot io> ---
I ran into a similar issue with a completely different stack.
Here is the complete reproduction "playbook" on ubunty trusty:
https://github.com/ribasushi/gcc_asan_internal_fail/commit/191e08bab6714b32615e51375fcaf871b6c5d245#diff-354f30a63fb0907d4ad57269548329e3R22
Results:
https://travis-ci.org/ribasushi/gcc_asan_internal_fail/builds/359301514#L1992
You can trigger a build by simply issuing a pull request against the
repository:
https://github.com/ribasushi/gcc_asan_internal_fail
Please note - I *am* aware the ODBC driver compilation is riddled with
warnings. This is an auxiliary concern to what I was trying to test, and what
tripped up gcc's sanitizer with an internal CHECK error.
