https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to urs from comment #2) > On Wed, Nov 16, 2022 at 02:41:40PM +0000, dmalcolm at gcc dot gnu.org wrote: > > Unfortunately I can't reproduce the ICE with the attachment. > > Yes, attachment was created with "-v -save-temps -freport-bug" and with that > the crash doesn't show up. Thanks! That seems to confirm my suspicion about what's crashing. I think it's crashing when the analyzer asks the C frontend for the value of one of these names: O_ACCMODE O_RDONLY O_WRONLY SOCK_STREAM SOCK_DGRAM but it's not clear to me how that could fail. It would be good to know which name it's failing on, and how it's defined/declared in your headers. If you're familiar with gdb, would you be able to reproduce the crasher under gdb, by adding: -wrapper gdb,--args to the crashing gcc invocation, and getting a backtrace at the point of the crash. Otherwise, would you be able to try rebuilding gcc with attachment 53911, and then use -fdump-analyzer, which with that patch ought to dump which name it's failing on (the dump is written to SOURCEFILE.analyzer.txt). Sorry about this.
