Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 615436 - [abrt] crash in php-cli-5.3.2-2.fc13: Process /usr/bin/php was killed by signal 6 (SIGABRT)
[abrt] crash in php-cli-5.3.2-2.fc13: Process /usr/bin/php was killed by sign...
Status: CLOSED DUPLICATE of bug 610034
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Joe Orton
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-16 14:01 EDT by Radu Alexandru Popescu
Modified: 2010-11-08 13:38 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-08 13:38:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (39.04 KB, text/plain)
2010-07-16 14:01 EDT, Radu Alexandru Popescu
no flags Details

  None (edit)
Description Radu Alexandru Popescu 2010-07-16 14:01:11 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/php /home/alex/workspace/testPHP/test1.php
comment: Aparently PHP is broken on x86_64. It crashes with every ocasion.
component: php
executable: /usr/bin/php
global_uuid: 99d7aa57ceb217f8666387dd4a010d7712c7f823
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)

How to reproduce
1. Create a simple PHP script in Eclipse.
2. Choose to debug the script.
Comment 1 Radu Alexandru Popescu 2010-07-16 14:01:14 EDT
Created attachment 432466 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 13:38:39 EST

*** This bug has been marked as a duplicate of bug 610034 ***
Comment 3 Karel Klíč 2010-11-08 13:38:39 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #610034.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.