php5 crashed with SIGSEGV in clone()

Bug #288349 reported by Tom Worley
This bug report is a duplicate of:  Bug #441406: php5 crashed with SIGSEGV in clone(). Edit Remove
34
This bug affects 2 people
Affects Status Importance Assigned to Milestone
php5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: php5

Another odd crash from php running a phpMyVersion script via cron

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb7150790:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/php5
NonfreeKernelModules: nvidia
Package: php5-cli 5.2.6-2ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/php /var/www/phpmyversion/trunk/phpMyVersion/readBinLog.php
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=/usr/bin:/bin
 LANG=en_GB.UTF-8
 SHELL=/bin/sh
Signal: 11
SourcePackage: php5
Stacktrace:
 #0 0xb7150790 in ?? ()
 #1 0xb7b167ee in clone () from /lib/tls/i686/cmov/libc.so.6
StacktraceTop:
 ?? ()
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: php5 crashed with SIGSEGV in clone()
Uname: Linux 2.6.27-7-generic i686
UserGroups:

Revision history for this message
Tom Worley (tom-worley) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
clone () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
arno_b (arno.b) wrote :

Please, can you try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash and on http://live.gnome.org/GettingTraces/Details.
(install packages 'php5-dbg' and 'gdb' and see here for backtrace https://wiki.ubuntu.com/Backtrace)

If it is a random crash, you can attach php within gdb and wait for a crash.

Marked as incomplete until we have a backtrace.

Changed in php5:
status: New → Incomplete
Revision history for this message
arno_b (arno.b) wrote :

By the way, Can you reproduce it?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in php5:
status: Incomplete → Invalid
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.