View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000594 | Xdebug | Uncategorized | public | 2010-07-14 10:49 | 2020-03-12 16:57 |
| Reporter | Devis | Assigned To | derick | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Product Version | 2.1.0 | ||||
| Summary | 0000594: Extend the scream support | ||||
| Description | It would be useful to have something similar to the scream option for var_dump(), print_r(), die(), exit(), __halt_compiler(), debug_print_backtrace and similar functions. The idea is to "scream" when one of this function is called, providing information such as FILE and LINE to understand why a script died or who is putting debug information in the output chain. This should make easier to clean the code and to understand why a third party library/framework/software is stopping. Note: print_r might be called with $return true, in such case there should be no "scream". | ||||
| Tags | No tags attached. | ||||
| Operating System | Any | ||||
| PHP Version | 5.3.3 | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-07-14 10:49 | Devis | New Issue | |
| 2010-07-14 10:49 | Devis | Operating System | => Any |
| 2010-07-14 10:49 | Devis | PHP Version | => 5.3.3 |
| 2010-07-14 10:49 | Devis | Xdebug Version | => 2.1.0 |
| 2014-02-27 19:06 | derick | Note Added: 0002679 | |
| 2014-02-27 19:06 | derick | Status | new => resolved |
| 2014-02-27 19:06 | derick | Resolution | open => won't fix |
| 2014-02-27 19:06 | derick | Assigned To | => derick |
| 2020-03-12 16:57 | derick | Category | Feature/Change request => Uncategorized |