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.

Description of problem:
I was debugging control-center crash but cannot generate backtrace as gdb says:
../../gdb/gdbarch.c:4229: internal-error: gdbarch_auto_charset: Assertion `gdbarch != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

and after two more steps it generates core dump.

backtrace attached

Version-Release number of selected component (if applicable):
gdb-7.6.1-64.el7.x86_64

How reproducible:
always

Steps to Reproduce:
0.start control-center and attach a gdb
1.crash control-center (adding/removing bond in network panel)
2.set logging on in gdb
3.generate backtrace via bt full

Actual results:
crash

Expected results:
no crash

Additional info:

Created attachment 1025001 [details]
backtrace

I am trying to reproduce the bug here, but I can't crash gnome-control-center by adding/removing bond in the network panel.  Could you give more detailed information on how to crash it?  Also, do you have debuginfo installed for control-center?  And what is the version of control-center you're using?  Thanks.

The backtrace looks exactly like Bug 1197665, why don't you consider this one as its duplicate?

You are right, Jan.

Vladimir, I am closing this bug as a duplicate of the Bug 1197665.  You can give a try on the scratch build that I made for Matej there:

  <https://brewweb.devel.redhat.com/taskinfo?taskID=8899649>

Thanks.

*** This bug has been marked as a duplicate of bug 1197665 ***