Ubuntu
php5 package

php5-fpm crashed with SIGSEGV

Bug #1063680 reported by Maarten Kossen on 2012-10-08

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	php5 (Ubuntu)	Invalid	Undecided	Unassigned

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
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
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
StacktraceTop:
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
Title: php5-fpm crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-08 (0 days ago)
UserGroups:

Tags:

Revision history for this message

Maarten Kossen (mpkossen) wrote on 2012-10-08:

#1

Dependencies.txt Edit (982 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (630 bytes, text/plain; charset="utf-8")
PHPInstalledModules.txt Edit (432 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (21.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (763 bytes, text/plain; charset="utf-8")
Registers.txt Edit (826 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-08:

#2

StacktraceTop:
?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2
?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2
?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2
?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2
?? () from /tmp/tmpTJx5y5/lib64/ld-linux-x86-64.so.2

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-08: Stacktrace.txt

#3

Stacktrace.txt Edit (2.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-08: StacktraceSource.txt

#4

StacktraceSource.txt Edit (1.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-08: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (2.6 KiB, text/plain)

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-08: Crash report cannot be processed

#6

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.