Bug 638995
Summary: | abrt-hook-ccpp[7975]: segfault at 0 ip 009b37f0 sp bffce538 error 4 in libc-2.12.1.so[93c000+185000] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | anton, bugzilla-redhat, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-15 18:35:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Orion Poplawski
2010-09-30 15:09:10 UTC
Orion, abrt is the "Automatic Bug Reporting Tool" and it picked up on the dump of your kftp binary which crashed. kftp wasn't part of an RPM signed by the Fedora gpg keys, so it did not report the crash back to the Fedora Project. Look at the config in /etc/abrt/abrt.conf to learn more. Now here is where I'd normally tell you to look at your kftp app and find out what it's doing wrong or to update it, but I'm having this libc-2.12.1.so crash as well with different applications as well in Fedora 13. So far, zfs-fuse and libvirtd. http://groups.google.com/group/zfs-fuse/browse_thread/thread/7e897ebf6acadc82 What hardware is this on? Dell Precision WorkStation 360 cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.40GHz stepping : 9 cpu MHz : 2400.000 Well, that's a dead end. The only odd thing that I'm doing is running a 2.6.36.1 kernel. Is there any chance you're running 2.6.36 ? Looks like it is fixed as of Oct 20. *** This bug has been marked as a duplicate of bug 652338 *** |