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/29783] New: [gdb, s390x] frame.c:1813: internal-error: get_selected_frame: Assertion `selected_frame != NULL' failed.
Date: Tue, 15 Nov 2022 08:11:40 +0000	[thread overview]
Message-ID: <bug-29783-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29783
           Summary: [gdb, s390x] frame.c:1813: internal-error:
                    get_selected_frame: Assertion `selected_frame != NULL'
                    failed.
           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: ---

With a gdb 12.1 based package on SLE-12, I ran into:
...
frame.c:1813: internal-error: get_selected_frame: Assertion `selected_frame !=
NULL' failed.
...
in test-case gdb.mi/user-selected-context-sync.exp:
...
-interpreter-exec console "frame"^M
&"warning: Couldn't restore frame #1 in current thread.  Bottom (innermost)
frame selected:\n\
"^M
~"#0  child_sub_function () at
/home/abuild/rpmbuild/BUILD/gdb-12.1/gdb/testsuite/gdb.mi/user-selected-context-sync.c:33\n"^M
~"33\t    dummy = !dummy; /* thread loop line */\n"^M
&"../../gdb/frame.c:1813: internal-error: get_selected_frame: Assertion
`selected_frame != NULL' failed.\nA problem internal to GDB has been
detected,\nfurther debugging may prove unreliable."^M
&"\n"^M
&"----- Backtrace -----\n"^M
&"Backtrace unavailable\n"^M
&"---------------------\n"^M
  ...
FAIL: gdb.mi/user-selected-context-sync.exp: mode=non-stop:
exec_mode=interpreter-exec: test_\
cli_in_mi_frame: thread 1.2: frame without args (timeout)
ERROR: GDB process no longer exists
GDB process exited with wait status 2046 exp9 0 0 CHILDKILLED SIGABRT SIGABRT
...

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

                 reply	other threads:[~2022-11-15  8:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-29783-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).