View Issue Details

IDProjectCategoryView StatusLast Update
0023944mantisbtbugtrackerpublic2018-02-06 21:17
Reporterdregad Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version2.11.0Fixed in Version2.11.0 
Summary0023944: The stack trace on detailed error page should not include the error handler itself
Description

The first entry in the stack trace on detailed error page (when $g_show_detailed_errors = ON) is the MantisBT error handler.

As shown on the attached screenshot, this does not add any value, as all of the useful data is already available elsewhere on the page (filename, line number, error code and type). The last parameter (context) is deprecated and should be removed (see 0023942).

To reduce clutter on the error page and provide only meaningful information to the administrator, the error handler should not be part of the displayed stack trace.

TagsNo tags attached.

Relationships

related to 0023943 closeddregad Improve detailed error page layout 
related to 0023942 closeddregad Remove deprecated "errcontext" parameter from standard error handler 

Activities

dregad

dregad

2018-02-06 17:03

developer  

Selection_004.png (92,070 bytes)   
Selection_004.png (92,070 bytes)   
dregad

dregad

2018-02-06 17:32

developer   ~0058782

PR https://github.com/mantisbt/mantisbt/pull/1286

Related Changesets

MantisBT: master 471e7ff7

2018-02-03 19:32:14

dregad


Committer: vboctor Details Diff
Stack trace should begin where error was triggered

Until now, the first entry in the stack trace was the MantisBT error
handler.

The reported stack now begins with the function call where the error was
actually triggered.

Instead of multiple array_shift() calls, we now rely on a single
array_slice().

Fixes 0023944
Affected Issues
0023944
mod - core/error_api.php Diff File