| Summary: | [abrt] gdb-7.1-29.el6_0.1: Process /usr/bin/gdb was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Red Hat Case Diagnostics <case-diagnostics> | ||||
| Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | qe-baseos-tools-bugs | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0 | ||||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:25c485d0ab0745fd1ca0d06498b113fb96a47d8c | ||||||
| Fixed In Version: | gdb-7.2-45.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-17 09:19:43 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Red Hat Case Diagnostics
2011-05-12 21:05:21 UTC
Created attachment 498632 [details]
File: backtrace
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Failed: get_frame_pc: gdb_assert (frame->next != NULL);
It cannot happen, the last (innermost) is create_sentinel_frame:
/* Link this frame back to itself. The frame is self referential
(the unwound PC is the same as the pc), so make it so. */
frame->next = frame;
I guess it is a memory corruption:
There was a memory corruption bug affecting MI - fixed in gdb-7.2-45.el6 (Bug 682891) shipped in RHEL-6.1.
One could also Z-Stream Bug 682891 for 6.0 but that is not being requested here.
CURRENTRELEASE is sure just a guess, memory corruptions are hard to identify.
|