Bug 2467251

Created attachment 2139702 [details]
File: proc_pid_status

Created attachment 2139703 [details]
File: maps

Created attachment 2139704 [details]
File: limits

Created attachment 2139705 [details]
File: environ

Created attachment 2139706 [details]
File: open_fds

Created attachment 2139707 [details]
File: mountinfo

Created attachment 2139708 [details]
File: os_info

Created attachment 2139709 [details]
File: cpuinfo

Created attachment 2139710 [details]
File: core_backtrace

Created attachment 2139713 [details]
File: dso_list

Created attachment 2139715 [details]
File: backtrace

The following upstream commits should fix this issue:

* d980317c7f1 gdb: int to bool conversion in valprint.{c,h}
* 958d06262a7 gdb: fix coerce_pieced_ref for multi-piece values
* 7d1d7386561 gdb: rename argument in valprint_check_validity
* 8915de0883c gdb: remove embedded_offset argument that is always 0
* 8f65ab7b71f gdb: use value::embedded_offset in check_pieced_synthetic_pointer

I opened the following PRs to backports these commits:

[F43] https://src.fedoraproject.org/rpms/gdb/pull-request/214
[F44] https://src.fedoraproject.org/rpms/gdb/pull-request/215
[Rawhide] https://src.fedoraproject.org/rpms/gdb/pull-request/216

All the PRs have now been merged.  The fix will be available once a new release is made on each branch.

FEDORA-2026-26cf29cfa1 (gdb-17.1-6.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-26cf29cfa1

FEDORA-2026-26cf29cfa1 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-26cf29cfa1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-26cf29cfa1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2026-26cf29cfa1 (gdb-17.1-6.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

As in https://bugzilla.redhat.com/show_bug.cgi?id=2483633#c0.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gdb killed by SIGABRT
journald_cursor: s=2c1910e140e64b2c86a6ef7504aaa761;i=70ae3;b=e6a4b02f1a2a45f08fe255bba80bfd2f;m=35505b402;t=6531e32e1fb78;x=4fff6db45fda245c
executable:     /usr/libexec/gdb
cmdline:        /usr/libexec/gdb -batch -ex $'set debuginfod enabled on' "" -ex $'file /usr/lib64/powershell/pwsh' -ex $'core-file ./coredump' -ex $'thread apply all -ascending backtrace full 1024' -ex $'info sharedlib' -ex $'print (char*)__abort_msg' -ex $'print (char*)__glib_assert_msg' -ex $'info all-registers' -ex disassemble
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.freedesktop.problems.applet
rootdir:        /
uid:            1000
kernel:         7.0.10-201.fc44.x86_64
package:        gdb-headless-17.1-6.fc44
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: dump_core
comment:        As in https://bugzilla.redhat.com/show_bug.cgi?id=2483633#c0.

Is https://bugzilla.redhat.com/show_bug.cgi?id=2467251#c17 a separate problem, or not a problem, etcetera? BTW, although I've cited https://bugzilla.redhat.com/show_bug.cgi?id=2483633#c0 as the cause, it might also have merely occurred when I was debugging what I eventually reported to https://bugzilla.redhat.com/show_bug.cgi?id=2483634#c0, in `konsole` (invoked by `drkonqi-coredump-gui`), because I first needed to work around what https://github.com/abrt/gnome-abrt/issues/388#issue-3328247804 describes.

(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #18)
> Is https://bugzilla.redhat.com/show_bug.cgi?id=2467251#c17 a separate
> problem, or not a problem, etcetera? BTW, although I've cited
> https://bugzilla.redhat.com/show_bug.cgi?id=2483633#c0 as the cause, it
> might also have merely occurred when I was debugging what I eventually
> reported to https://bugzilla.redhat.com/show_bug.cgi?id=2483634#c0, in
> `konsole` (invoked by `drkonqi-coredump-gui`), because I first needed to
> work around what
> https://github.com/abrt/gnome-abrt/issues/388#issue-3328247804 describes.

IMO, problems in thunderbird and xwaylandvideobridge should not be causing
problems like the one in this bug.  Also, past investigations do not
suggest a link between OOM problems and GDB ABRT failures.  These are likely
problems in GDB.  That said, if you are seeing system instability problems,
those could cause random crashes in pretty much any utility, including GDB.

Created attachment 2143780 [details]
`/var/spool/abrt/ccpp-2026-05-31-15:50:28.359916-278824`

I've no particular system instability. If I correctly understand that “These are likely problems in GDB” means that https://bugzilla.redhat.com/show_bug.cgi?id=2467251#c17 might be actionable, attached is all that I can provide about it, if of any use. All that it lacks is the core, but the backtrace is present.

Perhaps, like https://bugs.kde.org/show_bug.cgi?id=520792#c2:~:text=Did%20you%20look%20at%20%60%23c1%60%20at%20RedHat%20Bugzilla%3F%20If%20so%2C%20that%27s%20not%20my%20report%2E%20My%20sole%20corroboration%2C%20there%2C%20is%20what%20little%20Abrt%20submitted%2C%20at%20https://bugzilla%2Eredhat%2Ecom/show_bug%2Ecgi%3Fid=2477822%23c13%2C%20for%20me%2E%20Abrt%20can%20erroneously%20collate%20unrelated%20crashes%2E, https://bugzilla.redhat.com/show_bug.cgi?id=2467251#c17 should have been a separate report…

Might https://bugzilla.redhat.com/show_bug.cgi?id=2500776#c0 be relevant?

If https://bugzilla.redhat.com/show_bug.cgi?id=2500776 was correctly categorized, then, no, I don't think it's relevant here.  That said, it's possible that marking it as a duplicate of the recent use-after-free problem was not correct.  If the bug mentioned there is still a problem in gdb-17.2-2.fc44 (or any other current Fedora release), then we should definitely take a closer look at it.  (And it's relevance to this ticket would still have to be determined.)