Bug #80881 [Fbk]: open_basedir crashes Apache

From: Date: Thu, 18 Mar 2021 17:48:59 +0000
Subject: Bug #80881 [Fbk]: open_basedir crashes Apache
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-232859@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=80881&edit=1

 ID:                 80881
 Updated by:         cmb@php.net
 Reported by:        simbiat at outlook dot com
 Summary:            open_basedir crashes Apache
 Status:             Feedback
 Type:               Bug
 Package:            Safe Mode/open_basedir
 Operating System:   Windows 10.0.19042.868]
 PHP Version:        8.0.3
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

> […] but I've used the build from Apache Lounge.

Do they provide their own PHP binaries?  If so, official PHP on
Windows debug packs will not work.  I have not been able to attach
x64 nor x86 pdbs.

> Oh and my OneDrive is not in on-demand mode. I do not use this
> feature.

That is super strange, because in that case C:\Users\simbi\OneDrive
should be a normal folder.  Again, please provide the output of

    fsutil reparsePoint query C:\Users\simbi\OneDrive


Previous Comments:
------------------------------------------------------------------------
[2021-03-18 16:57:15] simbiat at outlook dot com

Oh and my OneDrive is not in on-demand mode. I do not use this feature.

------------------------------------------------------------------------
[2021-03-18 16:55:50] simbiat at outlook dot com

I can try using Debug Diagnostic Tool, but I've used the build from Apache Lounge. Will the
debug pack from https://windows.php.net/download/
work with them?

------------------------------------------------------------------------
[2021-03-18 16:25:59] cmb@php.net

> Based on that manual, should not the full dump that was
> generated by Windows for httpd.exe be enough?

Well, I'm not a big fan of downloading 2 GB crash dumps, but I
might give it a try.

> Also I'm not sure I understand what you mean by "on-demand" […]

You can have your local OneDrive folder in on-demand mode, or you
can copy the files.  In the former case, the OneDrive folder is a
reparse point.

> […] and why it's normal for Apache to crash this way.

I don't know; I didn't say this.

------------------------------------------------------------------------
[2021-03-18 16:19:39] simbiat at outlook dot com

Based on that manual, should not the full dump that was generated by Windows for httpd.exe be
enough? It can be taken from https://1drv.ms/u/s!AsaK_C2Xv0I4gunuXIptXRyLcx8YymA?e=NmL4AA

Also I'm not sure I understand what you mean by "on-demand" and why it's normal
for Apache to crash this way. From what I understand "ondemand" is relevant for PHP-FPM,
but it's not available for Windows, from what I know. I was able to replciate the crash with
mod_php and mod_fcgi.

------------------------------------------------------------------------
[2021-03-18 12:16:24] cmb@php.net

> open_basedir = "C:/Users/simbi/OneDrive/…"
> […] if you set open_basedir it will slow PHP down and cause
> Apache to crash.

Assuming you have on-demand enabled, the former is to be expected.
You're generally better off to download a copy of the Website and
work with this.

The stack backtrace would be way more helpful, if you had debug
symbols for PHP installed.  You can get them from windows.php.net;
they're called "debug pack".  Then generate a stack backtrace[1]
with the Debug Diagnostic Tool and make sure that the debug
symbols are loaded.

Also, it might help if you can provide the output of

    fsutil reparsePoint query C:\Users\simbi\OneDrive

[1] <https://bugs.php.net/bugs-generating-backtrace-win32.php>

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=80881


--
Edit this bug report at https://bugs.php.net/bug.php?id=80881&edit=1


Thread (18 messages)

« previous php.bugs (#232859) next »