|Summary:||[abrt] crash in php-cli-5.3.2-2.fc13: Process /usr/bin/php was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||John <audit.art>|
|Component:||zarafa||Assignee:||Robert Scheck <redhat-bugzilla>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||fedora, jorton, redhat-bugzilla, rpm, vanmeeuwen+fedora|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-27 17:24:54 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description John 2010-06-03 11:47:42 UTC
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: php -r 'echo rand(0,10);' component: php executable: /usr/bin/php global_uuid: b16538293d03958b55daa1632ad647c177617385 kernel: 22.214.171.124-112.fc13.x86_64 package: php-cli-5.3.2-2.fc13 rating: 4 reason: Process /usr/bin/php was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard)
Comment 2 Joe Orton 2010-06-03 12:17:48 UTC
The crash is deep inside a C++ constructor function in libvime, linked in via php-mapi, part of the zarafa package.
Comment 3 Robert Scheck 2010-06-03 12:25:04 UTC
John, are you able to reproduce that using "php -r 'echo rand(0,10);'"?
Comment 4 Remi Collet 2010-06-03 17:52:46 UTC
*** Bug 599062 has been marked as a duplicate of this bug. ***
Comment 5 John 2010-06-04 11:56:16 UTC
(In reply to comment #3) > John, are you able to reproduce that using "php -r 'echo rand(0,10);'"? reproduce available after commenting mapi.so extension into file "/etc/php.d/zarafa.ini" e.g: ; Enable Zarafa mapi extension module ; extension=mapi.so
Comment 6 Robert Scheck 2010-06-06 23:18:51 UTC
Notified upstream about this - even I'm still not able to reproduce this issue. May you please provide the output of "rpm -qa | grep ^php-" here?
Comment 7 Joe Orton 2010-06-07 07:27:06 UTC
If you can reproduce the crash without zarafa configured, can you please provide a new backtrace? Try: gdb --args php -r 'echo rand(0,10);' | tee php.debug ... (gdb) run ...crash... (gdb) bt full ... (gdb) quit and then attack "php.debug" to this bug report.
Comment 8 Robert Scheck 2010-09-13 00:36:41 UTC
John, is the issue still reproducible with php-mapi-6.40.2 (updates-testing)?
Comment 9 Bug Zapper 2011-06-02 12:14:00 UTC
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 10 Bug Zapper 2011-06-27 17:24:54 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.