Req #76274 [Sus]: FatalExceptions don't include variables and stack traces under some conditions

Edit report at https://bugs.php.net/bug.php?id=76274&edit=1 ID: 76274 User updated by: archon810 at gmail dot com Reported by: archon810 at gmail dot com Summary: FatalExceptions don't include variables and stack traces under some conditions Status: Suspended Type: Feature/Change Request Package: Scripting Engine problem Operating System: Linux PHP Version: 7.2.5 Block user comment: N Private report: N New Comment: The PHP mailing list's archaic software is quite frustrating to use. I tried subscribing to the PHP Internals list http://php.net/mailing-lists.php several times, but no emails arrive to complete the subscription, so I can't send a message out. Why can't we just have a normal forum these days instead of these prehistoric mailing lists that don't have the ability to post a message without subscribing to everything first? ezmlm is as user-friendly to interface with now as it was 20 years ago. Previous Comments: ------------------------------------------------------------------------ [2018-04-28 00:21:00] requinix@php.net I understand that, but this bug tracker is not the best place to interact with the "core devs" and it is not suitable for discussions or conversations that go beyond simple Q&A. That's what the mailing list is for. This report isn't closed. Suspended means just that: suspended, and pending discussion about what to do with it. ------------------------------------------------------------------------ [2018-04-28 00:06:27] archon810 at gmail dot com @requinix It's not clear to me whether this is a bug/feature report or there's a solution Sentry isn't seeing, hence filing here. We're looking for feedback from the core devs and a possible enhancement in core PHP. ------------------------------------------------------------------------ [2018-04-27 01:47:50] requinix@php.net This is but a lowly bug tracker. Try the internals mailing list. https://secure.php.net/mailing-lists.php ------------------------------------------------------------------------ [2018-04-26 23:13:56] archon810 at gmail dot com I'm going to defer to the Sentry dev I've been conversing with, but it is my understanding that it's PHP that doesn't provide those variables in the event of, say, an OOM fatal exception, thus even if you freed up some memory, the data wouldn't be there to grab. In other words, it's PHP that isn't giving us the data rather than Sentry. ------------------------------------------------------------------------ [2018-04-26 23:02:57] hanskrentel at yahoo dot de you can do in PHP userland, at the beginning of your app (and before the error handler is triggered), reserve some memory (e.g. by assigning a larger string to a global variable), then when the error is triggered and w/ the problems you talk about, free that buffer. ------------------------------------------------------------------------ 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=76274 -- Edit this bug report at https://bugs.php.net/bug.php?id=76274&edit=1