Bug 915671

Summary: Truncated coredump with abrt-2.0.20, kernel 3.7.9-201.fc18.x86_64
Product: [Fedora] Fedora Reporter: Paul Lipps <paul.lipps>
Component: abrtAssignee: Denys Vlasenko <dvlasenk>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: abrt-devel-list, dvlasenk, iprikryl, jfilak, mmilata, mtoman, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b6cff96a06f5107cc0ec101a53802ba2cb227981
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 23:04:26 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:
Attachments:
Description Flags
Entire directory of ccpp from arbt
none
Entire directory of ccpp from arbt
none
Truncated coredump none

Description Paul Lipps 2013-02-26 10:06:17 UTC
Description of problem:
Process /user/bin/nepomukservicestub was killed by signal 11 (SIGSEGV) - abrt

--- Running report_uReport ---
Generating backtrace
eu-unstrip: No modules recognized in core file
Running eu-unstrip failed
Server side error: '"Validation failed: missing mandatory element 'core_backtrace'"'
(exited with 1)

Version-Release number of selected component:
abrt-2.0.20

Additional info:
kernel:         3.7.9-201.fc18.x86_64
type:           libreport

Comment 1 Jiri Moskovcak 2013-02-26 11:11:55 UTC
Can you please send us the core of the crashed application? It should be in $HOME/.cache/abrt/ccpp-<something>

Comment 2 Paul Lipps 2013-02-26 12:00:53 UTC
Created attachment 702824 [details]
Entire directory of ccpp from arbt

~/.cache/abrt/spool/ccpp-2013-02-26-04:02:21-1855/

Comment 3 Jiri Moskovcak 2013-02-27 12:49:01 UTC
Thank you for the effort, but unfortunately that archive is empty, can you please re-pack it and re-upload it?

Comment 4 Paul Lipps 2013-02-28 02:56:17 UTC
Created attachment 703758 [details]
Entire directory of ccpp from arbt

Output of ~/.cache/abrt/spool/ccpp-2013-02-26-04:02:21-1855

Comment 5 Denys Vlasenko 2013-09-06 11:34:08 UTC
The coredump is truncated. I'm attaching it separately.

Comment 6 Denys Vlasenko 2013-09-06 11:36:03 UTC
Created attachment 794671 [details]
Truncated coredump

ELF utilities balk on it in various ways:

$ objdump -drsx coredump
objdump: coredump: File truncated
$ eu-unstrip --core=coredump -n
eu-unstrip: No modules recognized in core file
$ readelf -aW coredump >OUT
readelf: Error: Unable to read in 0x8398 bytes of notes

Comment 7 Denys Vlasenko 2013-11-05 15:02:49 UTC
I propose that we file a kernel bug "allow coredump helper to know when kernel truncates the coredump".

Currently, kernel sends coredump data to the helper over a pipe.
Pipes (so far) have no facility to report errors from writer to reader: writer can only close the fd, resulting in EOF on reader's side.
What we want here is to get a -ESOMEERROR on reader side when kernel discovers that it can't finish the coredump correctly - and there *are* cases when that happens.

Comment 8 Fedora End Of Life 2013-12-21 15:24:34 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2014-02-05 23:04:26 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.