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/31061] New: [gdb] intrusive_list.h:458: internal-error: erase_element: Assertion `elem_node->prev != INTRUSIVE_LIST_UNLINKED_VALUE' failed
Date: Mon, 13 Nov 2023 12:55:21 +0000	[thread overview]
Message-ID: <bug-31061-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31061
           Summary: [gdb] intrusive_list.h:458: internal-error:
                    erase_element: Assertion `elem_node->prev !=
                    INTRUSIVE_LIST_UNLINKED_VALUE' failed
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I build a recent trunk (commit ae86085027a Automatic date update in version.in)
on pinebook (64-bit kernel, 32-bit userland) with gcc 10.2.1 and ran into:
...
/home/rock/gdb/src/gdb/../gdbsupport/intrusive_list.h:458: internal-error:
erase_element: Assertion `elem_node->prev != INTRUSIVE_LIST_UNLINKED_VALUE'
failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
----- Backtrace --FAIL: gdb.base/gdb-sigterm.exp: pass=1: expect eof (GDB
internal error)
Resyncing due to internal error.
---^M
0xaae39795 gdb_internal_backtrace_1^M
        /home/rock/gdb/src/gdb/bt-utils.c:122^M
0xaae3982f _Z22gdb_internal_backtracev^M
        /home/rock/gdb/src/gdb/bt-utils.c:168^M
0xab277015 internal_vproblem^M
        /home/rock/gdb/src/gdb/utils.c:396^M
0xab27738b _Z15internal_verrorPKciS0_St9__va_list^M
        /home/rock/gdb/src/gdb/utils.c:476^M
0xab426c17 _Z18internal_error_locPKciS0_z^M
        /home/rock/gdb/src/gdbsupport/errors.cc:58^M
0xaae2ec2f
_ZN14intrusive_listI10breakpoint19intrusive_base_nodeIS0_EE13erase_elementERS0_^M
        /home/rock/gdb/src/gdb/../gdbsupport/intrusive_list.h:458^M
0xaae2a87f ???^M
0xaae1d42b _Z17delete_breakpointP10breakpoint^M
        /home/rock/gdb/src/gdb/breakpoint.c:12636^M
0xab1ed045 delete_thread_breakpoint^M
        /home/rock/gdb/src/gdb/thread.c:98^M
0xab1ed0ab _Z30delete_single_step_breakpointsP11thread_info^M
        /home/rock/gdb/src/gdb/thread.c:123^M
0xab021e81 delete_thread_infrun_breakpoints^M
        /home/rock/gdb/src/gdb/infrun.c:3733^M
0xab021edd for_each_just_stopped_thread^M
        /home/rock/gdb/src/gdb/infrun.c:3752^M
0xab021f79 delete_just_stopped_threads_infrun_breakpoints^M
        /home/rock/gdb/src/gdb/infrun.c:3768^M
0xaae2c629 _ZN10scope_exitIPFvvEE7on_exitEv^M
        /home/rock/gdb/src/gdb/../gdbsupport/scope-exit.h:150^M
0xaae28533 _ZN15scope_exit_baseI10scope_exitIPFvvEEED2Ev^M
        /home/rock/gdb/src/gdb/../gdbsupport/scope-exit.h:68^M
---------------------^M
  [infrun] infrun_async: enable=0^M
/home/rock/gdb/src/gdb/../gdbsupport/intrusive_list.h:458: internal-error:
erase_element: Assertion `elem_node->prev != INTRUSIVE_LIST_UNLINKED_VALUE'
failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n)   [infrun] scoped_disable_commit_resumed:
reason=killing^M
  [infrun] reset: reason=killing^M
n^M
ERROR: Could not resync from internal error (eof)
gdb.base/gdb-sigterm.exp: pass=1: expect eof: stepped 5 times
UNRESOLVED: gdb.base/gdb-sigterm.exp: 50 SIGTERM passes
...

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

             reply	other threads:[~2023-11-13 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 12:55 vries at gcc dot gnu.org [this message]
2023-11-13 12:55 ` [Bug gdb/31061] " vries at gcc dot gnu.org
2023-11-13 15:25 ` vries at gcc dot gnu.org
2023-11-13 15:26 ` vries at gcc dot gnu.org
2023-11-29 11:58 ` vries at gcc dot gnu.org
2024-01-24 15:00 ` sam at gentoo dot org
2024-01-24 15:00 ` sam at gentoo 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-31061-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).