public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/28908] Assertion `strstr (name, "::") == NULL' failed. listing member function names of a namespace class Date: Fri, 18 Feb 2022 21:54:02 +0000 [thread overview] Message-ID: <bug-28908-4717-zvCuWhlhpd@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28908-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28908 --- Comment #1 from Martin Sebor <msebor at gmail dot com> --- The full stack trace with trunk is below: /src/binutils-gdb/gdb/cp-namespace.c:178: internal-error: cp_lookup_bare_symbol: Assertion `strstr (name, "::") == NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x4cbb63 gdb_internal_backtrace_1 /src/binutils-gdb/gdb/bt-utils.c:122 0x4cbb63 _Z22gdb_internal_backtracev /src/binutils-gdb/gdb/bt-utils.c:168 0x80ba44 internal_vproblem /src/binutils-gdb/gdb/utils.c:394 0x80bc58 _Z15internal_verrorPKciS0_P13__va_list_tag /src/binutils-gdb/gdb/utils.c:471 0x9206f1 _Z14internal_errorPKciS0_z /src/binutils-gdb/gdbsupport/errors.cc:55 0x53990c cp_lookup_bare_symbol /src/binutils-gdb/gdb/cp-namespace.c:178 0x539ab7 cp_lookup_symbol_in_namespace /src/binutils-gdb/gdb/cp-namespace.c:325 0x53a3b7 lookup_namespace_scope /src/binutils-gdb/gdb/cp-namespace.c:724 0x53a46b _Z25cp_lookup_symbol_nonlocalPK13language_defnPKcPK5block15domain_enum_tag /src/binutils-gdb/gdb/cp-namespace.c:754 0x792d1e lookup_symbol_aux /src/binutils-gdb/gdb/symtab.c:2161 0x792e62 _Z25lookup_symbol_in_languagePKcPK5block15domain_enum_tag8languageP20field_of_this_result /src/binutils-gdb/gdb/symtab.c:1953 0x646b91 find_label_symbols_in_block /src/binutils-gdb/gdb/linespec.c:4009 0x646d8b find_label_symbols /src/binutils-gdb/gdb/linespec.c:4053 0x64a6db linespec_parse_basic /src/binutils-gdb/gdb/linespec.c:1909 0x64a6db parse_linespec /src/binutils-gdb/gdb/linespec.c:2677 0x64aedb event_location_to_sals /src/binutils-gdb/gdb/linespec.c:3159 0x64c33d _Z13decode_line_1PK14event_locationiP13program_spaceP6symtabi /src/binutils-gdb/gdb/linespec.c:3293 0x4f8261 list_command /src/binutils-gdb/gdb/cli/cli-cmds.c:1256 0x4fbf74 _Z8cmd_funcP16cmd_list_elementPKci /src/binutils-gdb/gdb/cli/cli-decode.c:2514 0x7ceac1 _Z15execute_commandPKci /src/binutils-gdb/gdb/top.c:670 0x5c4e6c _Z15command_handlerPKc /src/binutils-gdb/gdb/event-top.c:597 0x5c518a _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE /src/binutils-gdb/gdb/event-top.c:782 0x5c57ab gdb_rl_callback_handler /src/binutils-gdb/gdb/event-top.c:229 0x84b897 rl_callback_read_char /src/binutils-gdb/readline/readline/callback.c:281 0x5c40bd gdb_rl_callback_read_char_wrapper_noexcept /src/binutils-gdb/gdb/event-top.c:187 0x5c569c gdb_rl_callback_read_char_wrapper /src/binutils-gdb/gdb/event-top.c:204 0x5c3d6f _Z19stdin_event_handleriPv /src/binutils-gdb/gdb/event-top.c:524 0x920fad gdb_wait_for_event /src/binutils-gdb/gdbsupport/event-loop.cc:700 0x92121c gdb_wait_for_event /src/binutils-gdb/gdbsupport/event-loop.cc:596 0x92121c _Z16gdb_do_one_eventv /src/binutils-gdb/gdbsupport/event-loop.cc:237 0x675e24 start_event_loop /src/binutils-gdb/gdb/main.c:421 0x675e24 captured_command_loop /src/binutils-gdb/gdb/main.c:481 0x677774 captured_main /src/binutils-gdb/gdb/main.c:1348 0x677774 _Z8gdb_mainP18captured_main_args /src/binutils-gdb/gdb/main.c:1363 0x431b34 main /src/binutils-gdb/gdb/gdb.c:32 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-18 21:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 21:53 [Bug c++/28908] New: " msebor at gmail dot com 2022-02-18 21:54 ` msebor at gmail dot com [this message] 2022-02-24 15:06 ` [Bug c++/28908] " tromey at sourceware dot org 2023-12-30 15:45 ` ssbssa at sourceware dot 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-28908-4717-zvCuWhlhpd@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).