I suggest you ...

Visual Studio Sequencial Breakpoints... and breakpoint naming

As software engineers we have a lot of debugging to to..
Most problems do not occur in specific modules but in chains - catastrophic chains.

So a "In-Chain" debug feature would be SUPER helpful.
Set a breakpoint, that will "enable" another .. and so on.

In this way we could test sequential scenarios. Not just "points in time"

Something EXTRA like "naming" a breakpoint will enable "macro-like debug scenarios".

Those could be linked with our projects and will validate/catch REAL "run time" problems..

!0x..

26 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Elvis Nica shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Vincent Zalzal commented  ·   ·  Flag as inappropriate

    A simplified version of this would be to enhance the current "Hit count" condition. If we could specify a breakpoint label here, in the condition dialog, then we could say "enable this breakpoint after breakpoint A has been hit at least once", for example.

    I would really like this feature, and would probably use it every week.

  • Elvis Nica commented  ·   ·  Flag as inappropriate

    A breakpoint name could be like a "global" context. Will know where it is and call functions or read parameters values.

    Like:

    Set Breakpoint in file.cs (line no, module name, ...)
    Set breakpoint name=BRK_1,

    ...
    BRK_2: depends of BRK_1
    BRK_3: depends of BRK_2
    BRK_4: depends of BRK_2

    ...
    Then we could write a "macro code like"...
    if (${BRK_1}.local_var_name == 20 && ${BRK_2}.local_function(...) == true)
    {
    Debug.WriteLine(...)
    }

Feedback and Knowledge Base