diff --git a/docs/user_guide.adoc b/docs/user_guide.adoc index 52ee6adc..ed93d636 100644 --- a/docs/user_guide.adoc +++ b/docs/user_guide.adoc @@ -900,13 +900,17 @@ When clicking on a highlighted form two things can happen : image::user_guide_images/loops.png[] -==== Exception debugging +==== Exceptions debugging -If you are using _ClojureStorm_ you can jump to the last captured exception by evaluating the `:ex` keyword on your repl. This -will position the debugger right before the exception so you can step backwards and explore the cause. +`FlowStorm` will report all functions that didn't return because an exception unwind the stack, even +when that exception was captured further and it didn't bubble up. -If you are using vanilla or using _FlowStorm_ with ClojureScript, most of the time you can accomplish the same by clicking the `Step last` button -right after the exception happens. +image::user_guide_images/exceptions.png[] + +When an unwind situation is recorded a combobox will show up in the toolbar, containing all the functions names +together with the exceptions types. If you hover the mouse over any of them, a tooltip will display the exception message. + +Clicking on any of them will position the stepper at that point in time so you can explore what happened before. ==== Locals diff --git a/docs/user_guide.html b/docs/user_guide.html index cbb40fff..3cf4fd83 100644 --- a/docs/user_guide.html +++ b/docs/user_guide.html @@ -714,7 +714,7 @@

FlowStorm debugger User’s Guide

  • Power stepping
  • Searching
  • Loops
    • -
  • Exception debugging
    • +
  • Exceptions debugging
  • Locals
  • Stack
  • Value panels
    • @@ -2207,14 +2207,22 @@
    -
    Exception debugging
    +
    Exceptions debugging
    -

    If you are using ClojureStorm you can jump to the last captured exception by evaluating the :ex keyword on your repl. This -will position the debugger right before the exception so you can step backwards and explore the cause.

    +

    FlowStorm will report all functions that didn’t return because an exception unwind the stack, even +when that exception was captured further and it didn’t bubble up.

    +
    +
    +
    +exceptions +
    +
    +
    +

    When an unwind situation is recorded a combobox will show up in the toolbar, containing all the functions names +together with the exceptions types. If you hover the mouse over any of them, a tooltip will display the exception message.

    -

    If you are using vanilla or using FlowStorm with ClojureScript, most of the time you can accomplish the same by clicking the Step last button -right after the exception happens.

    +

    Clicking on any of them will position the stepper at that point in time so you can explore what happened before.

    @@ -3587,7 +3595,7 @@

    -Last updated 2024-01-29 07:59:08 -0300 +Last updated 2024-02-01 11:15:34 -0300

    diff --git a/docs/user_guide_images/exceptions.png b/docs/user_guide_images/exceptions.png new file mode 100644 index 00000000..57f75962 Binary files /dev/null and b/docs/user_guide_images/exceptions.png differ