php5-fpm crashed with SIGSEGV

Bug #1063680 reported by Maarten Kossen on 2012-10-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
php5 (Ubuntu)

Bug Description

Happened during the update to Quantal.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: php5-fpm 5.4.6-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Mon Oct 8 12:21:49 2012
ExecutablePath: /usr/sbin/php5-fpm
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcCmdline: /usr/sbin/php5-fpm --fpm-config /etc/php5/fpm/php-fpm.conf
 PATH=(custom, no user)
 Segfault happened at: 0x7f1ad14348e4: mov 0x8(%rax),%rax
 PC (0x7f1ad14348e4) ok
 source "0x8(%rax)" (0x7f1acdffee08) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: php5
 ?? () from /lib64/
 ?? () from /lib64/
 ?? () from /lib64/
 ?? () from /lib64/
 ?? () from /lib64/
Title: php5-fpm crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-08 (0 days ago)

Maarten Kossen (mpkossen) wrote :
visibility: private → public

 ?? () from /tmp/tmpTJx5y5/lib64/
 ?? () from /tmp/tmpTJx5y5/lib64/
 ?? () from /tmp/tmpTJx5y5/lib64/
 ?? () from /tmp/tmpTJx5y5/lib64/
 ?? () from /tmp/tmpTJx5y5/lib64/

Changed in php5 (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers