https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80498
--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to jonne from comment #13) > Thanks for all your help, Martin, I really appreciate. You're welcome. > > I re-ran with ASAN_OPTIONS as you suggested. The program seems to get killed > after about 44 seconds. Good. Then running that in gdb and pressing 'CTRL+C' after couple of seconds give you back-trace where it hangs. I would suspect an infinite loop, or enormous memory allocation that can eventually trigger the interrupt signal. I would double-check that. Good. So ASAN is initialized properly, but that does not help us how to catch the issue. My last question is about the warning produced by GCC. It can be also related.
