:orphan:

.. title:: CONFIG_EXTRA_EXCEPTION_INFO

.. kconfig:: CONFIG_EXTRA_EXCEPTION_INFO

CONFIG_EXTRA_EXCEPTION_INFO
###########################

*Extra exception debug information*

*Collect extra exception info*

Type: ``bool``

Help
====

.. code-block:: none

    Have exceptions print additional useful debugging information in
    human-readable form, at the expense of code size. For example,
    the cause code for an exception will be supplemented by a string
    describing what that cause code means.

Help
====

.. code-block:: none

    This option enables the collection of extra information, such as
    register state, when a fault occurs. This information can be useful
    to collect for post-mortem analysis and debug of issues.

Direct dependencies
===================

\ :kconfig:`NIOS2 <CONFIG_NIOS2>` || \ :kconfig:`ARCH_HAS_EXTRA_EXCEPTION_INFO <CONFIG_ARCH_HAS_EXTRA_EXCEPTION_INFO>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definitions
===================



At ``<Zephyr Architecture>/nios2/Kconfig:54``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39`` → ``<Zephyr Architecture>/Kconfig:12``

Menu path: (Top) → Nios II Options → Nios II Family Options

.. code-block:: kconfig

    config EXTRA_EXCEPTION_INFO
    	bool "Extra exception debug information"
    	depends on NIOS2
    	help
    	  Have exceptions print additional useful debugging information in
    	  human-readable form, at the expense of code size. For example,
    	  the cause code for an exception will be supplemented by a string
    	  describing what that cause code means.

----

At ``<Zephyr Architecture>/Kconfig:433``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39``

Menu path: (Top) → General Architecture Options → Interrupt Configuration

.. code-block:: kconfig

    config EXTRA_EXCEPTION_INFO
    	bool "Collect extra exception info"
    	depends on ARCH_HAS_EXTRA_EXCEPTION_INFO
    	help
    	  This option enables the collection of extra information, such as
    	  register state, when a fault occurs. This information can be useful
    	  to collect for post-mortem analysis and debug of issues.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*