user30341: What is the minimum debug level (TOOLS tab) which will display the stack trace on crash?
I would like to reduce information clutter in the serial monitor.
I understand that debug port must point to my serial monitor.
In case it makes a difference, it is a NodeMCU, running C++, in Arduino IDE on a Ubuntu 16.04 machine.

user37622: The crash report is printed to 'standard output' by __wrap_system_restart_local in core_esp8266_postmortem.c in esp8266 Arduino core. 
The standard output is considered as debug output in esp8266 Arduino core. Debug output to hardware Serial can be enabled in runtime by Serial.setDebugOutput(true);. 
At compile time the initial debug output is controled by -DDEBUG_ESP_PORT=, for example -DDEBUG_ESP_PORT=Serial1. The Tools menu "Debug port" sets the DEBUG_ESP_PORT define. The crash report is not controlled by "Debug level" setting.

30341: <p>What is the minimum <code>debug level</code> (<code>TOOLS</code> tab) which will display the stack trace on crash?</p>

<p>I would like to reduce information clutter in the serial monitor.</p>

<p>I understand that <code>debug port</code> must point to my serial monitor.</p>

<p>In case it makes a difference, it is a NodeMCU, running C++, in Arduino IDE on a Ubuntu 16.04 machine.</p>
 37622: <p>The crash report is printed to 'standard output' by <code>__wrap_system_restart_local</code> in <code>core_esp8266_postmortem.c</code> in esp8266 Arduino core. </p>

<p>The standard output is considered as debug output in esp8266 Arduino core. Debug output to hardware Serial can be enabled in runtime by <code>Serial.setDebugOutput(true);</code>. </p>

<p>At compile time the initial debug output is controled by <code>-DDEBUG_ESP_PORT=</code>, for example <code>-DDEBUG_ESP_PORT=Serial1</code>. The Tools menu "Debug port" sets the <code>DEBUG_ESP_PORT</code> define. The crash report is not controlled by "Debug level" setting.</p>
