| Summary: | gnome-settings-daemon ends up with SIGSEGV and drops an incomplete core | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-02 17:29:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Michal Jaegermann
2011-02-19 20:34:47 UTC
The kernel is responsible for dumping the core file, not gnome-settings-daemon itself. Is there a limit set for the core file size somewhere? (In reply to comment #2) > Is there a limit set for the core file size somewhere? No. On the system in question the core size is set to "unlimited". Is abrt capturing the core file? (In reply to comment #4) > Is abrt capturing the core file? Yes, this core file was captured by abrt. I have another core from gnome-settings-daemon produced few days later. If I look at it I see: Core was generated by `/usr/libexec/gnome-settings-daemon'. Program terminated with signal 11, Segmentation fault. and again: BFD: Warning: /var/spool/abrt/ccpp-1298347914-1715/coredump is truncated: expected core file size >= 45613056, found: 798720. AFAICS core files produces by other things are not truncated. This seems fairly similar to 759213 and there is a lot more information in that bug. Duping for now. *** This bug has been marked as a duplicate of bug 759213 *** |