I'm often find myself setting a breakpoint A somewhere in the code and manually enabling one or more breakpoints when this breakpoint is hit. A typical case is when I'm debugging an unittest and don't care about the preceding tests.
void testAddZeros()
{
Number a(0);
Number b(0);
Number result = a.add(b);
assert((a + b) == Number(0))
}
void testAddOnes()
{
Number a(1);
Number b(1);
Number result = a.add(b);
assert((a + b) == Number(2));
}
void testAddNegativeNumber()
{
Number a(1);
Number b(-1)
Number result = a.add(b);
assert((a + b) == Number(0));
}
Imagine if testAddZeros() and testAddOnes() runs fine, but testAddNegativeNumber(). In this case setting a breakpoint at Number result = a.add(b); would be a natural place to start debugging. Now imagine that the error is located somewhere deep inside Number::add, so we're not really interrested in the stuff that occurs early in Numbers::add. What I want to do is to set a breakpoint somewhere inside Numbers::add that only triggers if I'm inside the testAddNegativeNumber()-test.
Is there any way to automatically enable breakpoint B when breakpoint A is hit?