Slashdot Mirror

← Back to Stories (view on slashdot.org)

Debugging Asynchronous Applications?

Posted by Cliff on from the mind-your-breakpoints dept.

duncan bayne asks: "I'm attempting to debug a complicated telephony application, written in C#, that's almost entirely event driven. This is the first time I've debugged a large asynchronous application that isn't a GUI, and I'm curious to know what advice the Slashdot crowd has to share - have you any recommended tools, best practices, or common pitfalls to avoid?"

2 of 78 comments (clear)

  1. Debugging Asynchronous Applications For Dummies by Anonymous Coward · · Score: 3, Funny

    Chapter 1.

    Stand up and slowly back away from the keyboard.

    Chapter 2.

    There is no chapter 2.

  2. Re:Messages will get you by Joey+Vegetables · · Score: 3, Funny

    . . . deadlocks are going to be your enemies. Especially deadlocks.

    An easily vanquished enemy. Just log into Visual Haircut 2005 at least once a month or two, and don't forget to run the Help Me Stop Smoking Ganjj wizard as needed.

    --

    Nonaggression works!