Debug exception handler 

Functions of \TYPO3\CMS\Core\Error\DebugExceptionHandler :

  • Shows detailed exception messages and full trace of an exception.
  • Logs exception messages via the TYPO3 logging framework.
  • Logs exception messages to the sys_log table. Logged errors are displayed in the belog extension (Administration > Log). This will work only if there is an existing DB connection.

Copying a stack trace for a bug report 

A trace can leave the browser as text, so a report needs neither a screenshot nor a saved HTML file. The header of the page carries two buttons, and every file in the trace carries a third:

Exception page with the buttons Toggle details and Copy plaintext stack trace in its header, and a Copy path button beside the first file of the trace

The buttons the debug exception handler adds

Toggle details
Hides the file contents of every entry and brings them back, which turns the trace into a short overview.
Copy plaintext stack trace
Copies the whole trace as text, without the file contents.
Copy path
Copies that one file and its line number as path/to/File.php:42, with the project path cut off the front, so the result can be pasted into an editor that resolves paths from the project root.

A callout at the end of the trace says the same in the page itself, and asks you to look through the text for anything sensitive before passing it on.

Copying to the clipboard needs a secure context. Over plain HTTP a browser such as Firefox refuses it, the button then reports that it could not copy, and Copy plaintext stack trace writes the text into a box on the page instead, already selected to be copied by hand.