Bug 1286117

Summary:	SIGSEGV if xdebug.trace_output_dir file can not be created
Product:	[Fedora] Fedora	Reporter:	la_antorcha_guia
Component:	php-pecl-xdebug	Assignee:	Remi Collet <fedora>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	christof, fedora, pahan, redhat
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-29 17:01:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description la_antorcha_guia 2015-11-27 11:21:14 UTC

Description of problem:
If xdebug.trace_output_dir is set to non existent dir in zts-php, results in seg fault.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.xdebug.trace_output_dir to nonexistent directory
2. run zts-php, or php ?
3. seg fault

Actual results:
seg fault

Expected results:
Warning about xdebug configuration, dir or similar

Additional info:

Comment 1 Remi Collet 2015-11-27 11:54:41 UTC

Sorry, I cannot reproduce.

Can you please open an upstream bug on http://bugs.xdebug.org/ ?

Comment 2 la_antorcha_guia 2015-11-27 15:00:48 UTC

$strace zts-php zts-app.php
...
stat("OUTDIR/trace.out..xt", 0x7fff1e79ba90) = -1 ENOENT (No such file or directory)
open("OUTDIR/trace.out..xt", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++



$ mkdir -p OUTDIR 
Run without problems



# chown anotheruser:anotheruser OUTDIR


$strace zts-php zts-app.php
 +++ killed by SIGSEGV (core dumped) +++

Comment 3 Derick Rethans 2015-11-29 15:12:05 UTC

This has an Xdebug issue at http://bugs.xdebug.org/view.php?id=1215, which is resolved for the upcoming 2.4.0. You can consider this as "closed".

Comment 4 Remi Collet 2015-11-29 17:01:38 UTC

Thanks Derick


As this bug doesn't seems critical, because of a result of a miss-configuration, I close it, the upstream fix will be part of next build.