Re: How to get a PHP bug fixed?
| From: | Jáchym Toušek | Date: | Sat, 05 Jan 2013 22:20:11 +0000 |
| Subject: | Re: How to get a PHP bug fixed? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-64561@lists.php.net to get a copy of this message | ||
I've looked into it and I'm not sure whether an option for getTrace method is the best way to solve this. I mean the trace is created along with the exception so it would have to be generated with the object fields regardless and then filtered if the option is not set. I think it would be better to add new PHP directive for this (disabled by default for back compatibility).
Also what do you mean by DEBUG_BACKTRACE_*?
Dne Fri, 04 Jan 2013 21:59:19 +0100 Stas Malyshev <smalyshev@sugarcrm.com> napsal(a):
Hi!Hi, there is a bug(s) I'd like to be fixed and even a patch is available. But there is still no reaction at all after 2 years. What else can I do to get the bug(s) fixed?Pull request may speed things up, writing to internals might too :)https://bugs.php.net/bug.php?id=45351 - patch available from 2010-06-13This patch seems to do only part of the work - it does not add the option to getTrace, it does not use DEBUG_BACKTRACE_* constants and it does not have tests. If you are willing to get it to completion and submit a pull request with complete fix, it can be integrated pretty quickly,https://bugs.php.net/bug.php?id=48724 - patch available from 2012-04-13This one was waiting for maintainer's input.