Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1046089[details]
gedit coredump
Description of problem:
When trying to get a traceback from the attached core dump from the crash of gedit, I get after paging through couple of pages of the output of 'threads apply all backtrace' gdb crashes.
Version-Release number of selected component (if applicable):
gdb-7.6.1-65.el7.x86_64
How reproducible:
100% on the given coredump
Comment 4Sergio Durigan Junior
2015-07-06 21:23:08 UTC
Can you provide more info, please? Which version of gedit are you using? I have gedit-3.8.3-6.el7 here and cannot reproduce the crash (which happens with an unreleased GDB RPM, by the way). Thanks.
Neither gedit-3.14.3-4.el7 nor gdb-7.6.1-65.el7.x86_64 builds are available in Brew, they are already deleted there.
Without any text dumps here I really cannot do anything with this Bug.
Hopefully it could be for example Bug 1281351.
Created attachment 1046089 [details] gedit coredump Description of problem: When trying to get a traceback from the attached core dump from the crash of gedit, I get after paging through couple of pages of the output of 'threads apply all backtrace' gdb crashes. Version-Release number of selected component (if applicable): gdb-7.6.1-65.el7.x86_64 How reproducible: 100% on the given coredump