Bug 93409

Summary: lang/php5: PHP5 command line interpreter is dying with SIGSEGV
Product: Ports & Packages Reporter: Václav Haisman <v.haisman>
Component: Individual Port(s)Assignee: Alex Dupre <ale>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Václav Haisman 2006-02-15 21:30:04 UTC
The PHP5 CLI is dying with SIGSEGV as shown in the following excerpt from GDB session.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x82a9000 (LWP 100382)]
0x291c9350 in ?? ()
(gdb) bt
#0  0x291c9350 in ?? ()
#1  0x0812a882 in tsrm_shutdown () at /usr/ports/lang/php5/work/php-5.1.2/TSRM/TSRM.c:180
#2  0x082122cf in main (argc=1, argv=0xbfbfeac4)
    at /usr/ports/lang/php5/work/php-5.1.2/sapi/cli/php_cli.c:1240
(gdb) frame 1
#1  0x0812a882 in tsrm_shutdown () at /usr/ports/lang/php5/work/php-5.1.2/TSRM/TSRM.c:180
180                                                             resource_types_table[j].dtor(p->storage[j], &p->storage);
(gdb) print resource_types_table[j].dtor
$1 = 0x291c9350
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2006-02-16 09:24:08 UTC
Responsible Changed
From-To: freebsd-bugs->ale

Make it a ports bug and assign.
Comment 2 Václav Haisman 2006-04-22 17:10:16 UTC
Any progress with the bug? It is really annoying that I cannot use php
CLI without it dying.

--
VH
Comment 3 Alex Dupre freebsd_committer freebsd_triage 2006-05-23 07:21:58 UTC
State Changed
From-To: open->feedback

Do you have the same problem with 5.1.4?
Comment 4 Alex Dupre freebsd_committer freebsd_triage 2006-05-24 07:30:23 UTC
State Changed
From-To: feedback->closed

Submitter cannot test newer version and fixed the problem by disabling threads.