debugging tool
Jun. 20th, 2007 01:47 pmI would be interested in a general tool for figuring out who in the execution tree of the program is causing something to happen. We would define a set of events to watch for, like certain variables getting certain values or changing (and when to turn on/off the watch: otherwise this gets too inefficient), and it would print a stack trace + values of relevant variables whenever one of our events occurs.
This is a very simple idea, and very useful when you want to understand code that you didn't write. On the previous post that I wrote about this idea, different people said that what I wanted was "aspects", but that doesn't explain anything.
What tool do I want?
This is a very simple idea, and very useful when you want to understand code that you didn't write. On the previous post that I wrote about this idea, different people said that what I wanted was "aspects", but that doesn't explain anything.
What tool do I want?
(no subject)
Date: 2007-06-20 06:00 pm (UTC)(no subject)
Date: 2007-06-20 06:13 pm (UTC)(no subject)
Date: 2007-06-20 09:44 pm (UTC)(no subject)
Date: 2007-06-20 09:45 pm (UTC)(no subject)
Date: 2007-06-20 09:48 pm (UTC)(no subject)
Date: 2007-06-20 09:50 pm (UTC)Yeah, look at the keyword. Look at it very, very carefully. Follow the usage exactly.
And watch it cruelly, cruelly fail you.
(no subject)
Date: 2007-06-20 11:13 pm (UTC)-Eclipse has an extensive debugger