public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "urs at akk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107711] internal compiler error: Segmentation fault Date: Wed, 16 Nov 2022 19:41:44 +0000 [thread overview] Message-ID: <bug-107711-4-YcqKwZCdJ8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711 --- Comment #5 from urs at akk dot org --- On Wed, Nov 16, 2022 at 03:54:54PM +0000, dmalcolm at gcc dot gnu.org wrote: > 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. Program received signal SIGSEGV, Segmentation fault. 0x0000000000cf0871 in LINEMAPS_USED(line_maps const*, bool) () (gdb) bt #0 0x0000000000cf0871 in LINEMAPS_USED(line_maps const*, bool) () #1 0x0000000002e50aa3 in LINEMAPS_MACRO_USED(line_maps const*) () #2 0x0000000002e50adc in LINEMAPS_MACRO_LOWEST_LOCATION(line_maps const*) () #3 0x0000000002e7cd2e in linemap_location_from_macro_expansion_p(line_maps const*, unsigned int) () #4 0x0000000002e7c49d in linemap_lookup(line_maps const*, unsigned int) () #5 0x0000000002e7f752 in _cpp_warn_if_unused_macro () #6 0x0000000002e8a46d in ht_forall(ht*, int (*)(cpp_reader*, ht_identifier*, void const*), void const*) () #7 0x0000000002e6d9e6 in cpp_forall_identifiers(cpp_reader*, int (*)(cpp_reader*, cpp_hashnode*, void*), void*) () #8 0x0000000002e6f1b2 in cpp_finish(cpp_reader*, _IO_FILE*) () #9 0x0000000000d26427 in c_common_finish() () #10 0x000000000151a5f5 in finalize(bool) () #11 0x000000000151a966 in do_compile(bool) () #12 0x000000000151ad0e in toplev::main(int, char**) () #13 0x0000000002dded3e in main () > 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). See attachment
next prev parent reply other threads:[~2022-11-16 19:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 0:33 [Bug analyzer/107711] New: " urs at akk dot org 2022-11-16 14:41 ` [Bug analyzer/107711] " dmalcolm at gcc dot gnu.org 2022-11-16 15:26 ` urs at akk dot org 2022-11-16 15:50 ` dmalcolm at gcc dot gnu.org 2022-11-16 15:54 ` dmalcolm at gcc dot gnu.org 2022-11-16 19:41 ` urs at akk dot org [this message] 2022-11-16 19:50 ` urs at akk dot org 2022-11-16 21:15 ` [Bug analyzer/107711] ICE with -fanalyzer with -Wunused-macros since r13-4073-gd8aba860b34203 dmalcolm at gcc dot gnu.org 2022-11-16 22:45 ` [Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" " cvs-commit at gcc dot gnu.org 2022-11-16 23:18 ` dmalcolm at gcc dot gnu.org 2022-11-17 3:07 ` dmalcolm at gcc dot gnu.org 2022-11-17 17:36 ` cvs-commit at gcc dot gnu.org 2022-11-17 17:36 ` dmalcolm at gcc dot gnu.org 2022-11-28 22:24 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-107711-4-YcqKwZCdJ8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).