RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

i'm using gdb-10.2-10.el9.x86_64 on a rhel 9.1 nightly and when i have breakpoints set up, sometimes gdb has an internal error like:

../../gdb/jit.c:1278: internal-error: void jit_event_handler(gdbarch*, objfile*): Assertion `jiter->jiter_data != nullptr' failed.

an example of the kind of breakpoint commands that can cause this is:

(gdb) commands
Type commands for breakpoint(s) 2, one per line.
End with a line saying just "end".
>p rectangles[0]
>p rectangles[1]
>p rectangles[2]
>p rectangles[3]
>cont
>end

doing that after the breakpoint has been hit a few times, the assertion gets blown. This is in gnome-shell by the way which has llvmpipe running and javascript.

I've seen the issue in fedora before too, but never filed it until now.

(In reply to Ray Strode [halfline] from comment #0)
> 
> ../../gdb/jit.c:1278: internal-error: void jit_event_handler(gdbarch*,
> objfile*): Assertion `jiter->jiter_data != nullptr' failed.

This may have been addressed in an upstream commit that did not make 10.2:

commit 6d1a09b77a9ab52d9fc627b8f5eb952892c81f90
Author: Tom de Vries <tdevries>
Date:   Fri May 21 15:09:14 2021 +0200

    [gdb/breakpoint] Fix assert in jit_event_handler

I imagine this is not very easy to reproduce, but I can backport the
patch and provide you with a scratch build to try out.

Is that acceptable?

sure. it's not actually hard to reproduce so testing shouldn't be an issue. thanks

The scratch build you provided me in email with the fix from https://gitlab.com/keiths1/gdb/-/tree/2130624-jit_event_handler-assertion works great. Thank you.

Tested with gdb-10.2-11.el9.

Verified with gdb-10.2-11.el9.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: gdb security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6372