View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000187 | Xdebug | Uncategorized | public | 2006-06-07 10:04 | 2006-08-19 13:21 |
| Reporter | Tindu | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000187: stderr does not make XDebug report fatal errors | ||||
| Description | I want to get XDebug to report back fatal errors to me so I can show the line number or call stack to the user. Script: <? Log: Log opened at 2006-06-07 08:54:55 <- breakpoint_set -i 2 -t line -f file:///c:/rtw83/Train/test.php -n 5 <- stderr -i 1 -c 2 <- feature_set -i 1 -n max_depth -v 10 <- run -i 1 Log closed at 2006-06-07 08:54:55 | ||||
| Additional Information | In XDebug code: DBGP_FUNC(stderr) So not sure how this stderr could work... | ||||
| Tags | No tags attached. | ||||
| Operating System | Windows XP | ||||
| PHP Version | 5.1.2 | ||||
|
|
stderr is not supposed to work in the way you want this. I just committed a change to CVS that allows you to set an 'exception' breakpoint for the various PHP error types. Examples of this are: breakpoint_set -t exception -x "Fatal error" -s enabled -i 28 This feature should address what you were looking for. |