[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #10 from David Malcolm --- (In reply to Antoni from comment #9) > Created attachment 57810 [details] > Patch to fix the issue Looks reasonable. > I was unable to create a reproducer in C for the tests. > It seems the problem was ac

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #9 from Antoni --- Created attachment 57810 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57810&action=edit Patch to fix the issue I was unable to create a reproducer in C for the tests. It seems the problem was actually in l

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #8 from Antoni --- (In reply to David Malcolm from comment #2) > inlined_call_event's ctor should probably assert that params > tree apparent_callee_fndecl, > tree apparent_caller_fndecl, > are

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #7 from Antoni --- I don't know if this helps, but I added a small Rust reproducer that can trigger the segfault when compiled with rustc_codegen_gcc and the corresponding GIMPLE for this Rust reproducer.

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #6 from Antoni --- Created attachment 57439 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57439&action=edit Rust reproducer

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #5 from Antoni --- Created attachment 57438 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57438&action=edit GIMPLE for the Rust reproducer

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #4 from Antoni --- I might be able to soon create a reproducer, but for now, I can say it might be related to __attribute__ ((always_inline)).

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #3 from David Malcolm --- (In reply to David Malcolm from comment #2) > are both non-NULL, which might catch the issue slightly early. ^

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #2 from David Malcolm --- inlined_call_event's ctor should probably assert that params tree apparent_callee_fndecl, tree apparent_caller_fndecl, are both non-NULL, which might catch the iss

[Bug analyzer/113923] Segfault in gcc/gcc/tree-diagnostic.cc:265

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113923 --- Comment #1 from David Malcolm --- Reproducing that is going to be a challenge. FWIW you can probably work around it via -fno-analyzer-undo-inlining. For an inlined_call_event's m_apparent_caller_fndecl to be NULL, then when it was created