By Mike Deliman
When you're debugging a process, or a system, you never can be sure
were it will lead you. Sometimes you need special tools to find out
what's happened. Sometimes you just need a little extra visibility into
the system.
When you have a specific bit of code that runs, and that bit of code always fails the same way, you're at least starting with a defined test case and a known / expected failure syndrome. A real challenge is when the system seems to fail with a random set of symptoms - perhaps there are a few specific symptoms but you can't predict which will strike, or to what task, or when.
Subscribe
