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.

Description of problem:


Version-Release number of selected component:
gdb-7.2-60.el6_4.1

Additional info:
libreport version: 2.0.9
abrt_version:   2.0.8
backtrace_rating: 4
cmdline:        /usr/bin/gdb -nx --quiet --batch --readnever
crash_function: _IO_feof
kernel:         2.6.32-358.6.1.el6.x86_64

truncated backtrace:
:Thread no. 1 (8 frames)
: #0 _IO_feof at feof.c
: #1 find_charset_names at ../../gdb/charset.c
: #2 _initialize_charset at ../../gdb/charset.c
: #3 initialize_all_files at init.c
: #4 gdb_init at ../../gdb/top.c
: #5 captured_main at ../../gdb/main.c
: #6 catch_errors at ../../gdb/exceptions.c
: #7 gdb_main at ../../gdb/main.c

Hello,

I will need a reproducer for this bug, can you send one?  Just by seeing the truncated backtrace is very hard to understand what is wrong.

Thanks.

I don't have the system where the problem occured accessible (it's almost a year since reporting!)... IIRC the bug involved attaching gdb to running qemu process and gdb subsequently went unresponsive.