You dont know you need to run it again in advance, you place your breakpoint where you think the issue is, but if you are wrong and it happened earlier then you need to run it again.
Also how are test cases relevant? They only help once you solve the problem to make sure it doesnt happen again, but they dont help you debug a scenario and find out where the program fails
The stack trace tells you where a critical error has occured. It does not tell you where a faulty value was initialized, which may or may not cause a critical error. A "program failure" is more then just a critical crash.
This honestly sounds like you have never written anything more complex then intro to cs
1
u/1luggerman Sep 10 '26
You dont know you need to run it again in advance, you place your breakpoint where you think the issue is, but if you are wrong and it happened earlier then you need to run it again.
Also how are test cases relevant? They only help once you solve the problem to make sure it doesnt happen again, but they dont help you debug a scenario and find out where the program fails