public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29114] New: [gdb] breakpoint.c:11568: internal-error: insert_location: pure virtual function called
Date: Mon, 02 May 2022 09:29:39 +0000	[thread overview]
Message-ID: <bug-29114-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29114

            Bug ID: 29114
           Summary: [gdb] breakpoint.c:11568: internal-error:
                    insert_location: pure virtual function called
           Product: gdb
           Version: 12.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

When running test-case gdb.ada/catch_assert_if.exp, I run into:
...
FAIL: gdb.ada/catch_assert_if.exp: continuing to expected failed assertion (GDB
internal error)
FAIL: gdb.ada/catch_assert_if.exp: continuing to program completion (GDB
internal error)
...

First FAIL in more detail:
...
(gdb) PASS: gdb.ada/catch_assert_if.exp: Check catch assertions with condition
continue^M
Continuing.^M
/home/vries/gdb_versions/devel/src/gdb/breakpoint.c:11568: internal-error:
insert_location: pure virtual function called^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
----- Backtrace -----^M
FAIL: gdb.ada/catch_assert_if.exp: continuing to expected failed assertion (GDB
internal error)
Resyncing due to internal error.
0x55b97e gdb_internal_backtrace_1^M
        /home/vries/gdb_versions/devel/src/gdb/bt-utils.c:122^M
0x55ba21 _Z22gdb_internal_backtracev^M
        /home/vries/gdb_versions/devel/src/gdb/bt-utils.c:168^M
0xbab177 internal_vproblem^M
        /home/vries/gdb_versions/devel/src/gdb/utils.c:396^M
0xbab546 _Z15internal_verrorPKciS0_P13__va_list_tag^M
        /home/vries/gdb_versions/devel/src/gdb/utils.c:476^M
0xeb6736 _Z14internal_errorPKciS0_z^M
        /home/vries/gdb_versions/devel/src/gdbsupport/errors.cc:55^M
0x53bfbf _ZN10breakpoint15insert_locationEP11bp_location^M
        /home/vries/gdb_versions/devel/src/gdb/breakpoint.c:11568^M
0x525d0b insert_bp_location^M
        /home/vries/gdb_versions/devel/src/gdb/breakpoint.c:2718^M
0x526d0c insert_breakpoint_locations^M
        /home/vries/gdb_versions/devel/src/gdb/breakpoint.c:3120^M
0x53b94d update_global_location_list^M
        /home/vries/gdb_versions/devel/src/gdb/breakpoint.c:11404^M
0x52693e _Z18insert_breakpointsv^M
        /home/vries/gdb_versions/devel/src/gdb/breakpoint.c:3019^M
0x7f612f keep_going_pass_signal^M
        /home/vries/gdb_versions/devel/src/gdb/infrun.c:8247^M
0x7e7340 start_step_over^M
        /home/vries/gdb_versions/devel/src/gdb/infrun.c:2033^M
0x7e9ffa _Z7proceedm10gdb_signal^M
        /home/vries/gdb_versions/devel/src/gdb/infrun.c:3316^M
0x7d613e _Z10continue_1i^M
        /home/vries/gdb_versions/devel/src/gdb/infcmd.c:637^M
0x7d63f0 continue_command^M
        /home/vries/gdb_versions/devel/src/gdb/infcmd.c:729^M
0x5b28db do_simple_func^M
        /home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:95^M
0x5b74c7 _Z8cmd_funcP16cmd_list_elementPKci^M
        /home/vries/gdb_versions/devel/src/gdb/cli/cli-decode.c:2514^M
0xb17d72 _Z15execute_commandPKci^M
        /home/vries/gdb_versions/devel/src/gdb/top.c:699^M
0x72b136 _Z15command_handlerPKc^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:598^M
0x72b5de _Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:842^M
0xb417e9 tui_command_line_handler^M
        /home/vries/gdb_versions/devel/src/gdb/tui/tui-interp.c:278^M
0x72a932 gdb_rl_callback_handler^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:230^M
0xc1cfe5 rl_callback_read_char^M
        /home/vries/gdb_versions/devel/src/readline/readline/callback.c:287^M
0x72a7af gdb_rl_callback_read_char_wrapper_noexcept^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:188^M
0x72a836 gdb_rl_callback_read_char_wrapper^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:205^M
0x72af85 _Z19stdin_event_handleriPv^M
        /home/vries/gdb_versions/devel/src/gdb/event-top.c:525^M
0xeb7447 handle_file_event^M
        /home/vries/gdb_versions/devel/src/gdbsupport/event-loop.cc:574^M
0xeb79cf gdb_wait_for_event^M
        /home/vries/gdb_versions/devel/src/gdbsupport/event-loop.cc:700^M
0xeb68de _Z16gdb_do_one_eventv^M
        /home/vries/gdb_versions/devel/src/gdbsupport/event-loop.cc:237^M
0x863275 start_event_loop^M
        /home/vries/gdb_versions/devel/src/gdb/main.c:413^M
0x863395 captured_command_loop^M
        /home/vries/gdb_versions/devel/src/gdb/main.c:473^M
0x864bc5 captured_main^M
        /home/vries/gdb_versions/devel/src/gdb/main.c:1335^M
0x864c2b _Z8gdb_mainP18captured_main_args^M
        /home/vries/gdb_versions/devel/src/gdb/main.c:1350^M
0x41894d main^M
        /home/vries/gdb_versions/devel/src/gdb/gdb.c:32^M
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-05-02  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  9:29 vries at gcc dot gnu.org [this message]
2022-05-02  9:47 ` [Bug gdb/29114] " vries at gcc dot gnu.org
2022-05-02 10:25 ` vries at gcc dot gnu.org
2022-05-02 10:37 ` vries at gcc dot gnu.org
2022-05-02 10:43 ` vries at gcc dot gnu.org
2022-05-02 10:46 ` vries at gcc dot gnu.org
2022-05-02 14:37 ` tromey 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-29114-4717@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: link
Be 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).