php5 crashed with SIGSEGV in _Unwind_ForcedUnwind()

Bug #412501 reported by monah1744
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
php5 (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: php5

.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Aug 12 15:43:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/php5
Package: php5-cli 5.2.10.dfsg.1-1ubuntu1
ProcCmdline: /usr/bin/php /usr/share/obm/www/cron/cron.php
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x73e5fe: cmpw $0xb858,(%eax)
 PC (0x0073e5fe) ok
 source "$0xb858" ok
 destination "(%eax)" (0x050921ce) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: php5
StacktraceTop:
 ?? () from /lib/libgcc_s.so.1
 ?? () from /lib/libgcc_s.so.1
 _Unwind_ForcedUnwind () from /lib/libgcc_s.so.1
 _Unwind_ForcedUnwind ()
 __pthread_unwind () from /lib/tls/i686/cmov/libpthread.so.0
Title: php5 crashed with SIGSEGV in _Unwind_ForcedUnwind()
Uname: Linux 2.6.31-5-generic i686
UserGroups:

Revision history for this message
monah1744 (monah1744) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /lib/libgcc_s.so.1
?? () from /lib/libgcc_s.so.1
_Unwind_ForcedUnwind () from /lib/libgcc_s.so.1
_Unwind_ForcedUnwind ()
__pthread_unwind () from /lib/tls/i686/cmov/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in php5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Andreas Olsson (andol)
visibility: private → public
Revision history for this message
Andreas Olsson (andol) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 392521, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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