gusl: (Default)
[personal profile] gusl
I 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?

(no subject)

Date: 2007-06-20 06:00 pm (UTC)
From: [identity profile] dachte.livejournal.com
gdb can do it. Take a look at the "watch" keyword.

(no subject)

Date: 2007-06-20 09:50 pm (UTC)
From: [identity profile] bhudson.livejournal.com
HAHAHAHAHAHAthud.

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 06:13 pm (UTC)
From: [personal profile] chrisamaphone
strace is kind of like that but on the system level rather than the code level... it is a pretty neat tool anyway.

(no subject)

Date: 2007-06-20 09:44 pm (UTC)
From: [identity profile] douglasperkins.livejournal.com
Perhaps you have a particular language and platform in mind? Various IDEs have gdb-like things (or gdb) integrated with them.

(no subject)

Date: 2007-06-20 11:13 pm (UTC)
From: [identity profile] douglasperkins.livejournal.com
-jdb
-Eclipse has an extensive debugger

(no subject)

Date: 2007-06-20 09:48 pm (UTC)
From: [identity profile] gustavolacerda.livejournal.com
It would also be nice to know about such a tool for Lisp.

February 2020

S M T W T F S
      1
2345678
9101112131415
16171819202122
23242526272829

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags