Campbell Ritchie wrote:You can't sue the debugging facilities of an IDE to do that?
In the USA, you can sue anybody
Yeah, I know. My fingers don't work in the right order, either.
Tracing each and every method will quickly bury you alive and it's almost never either necessary or a good idea. If you really wanted to log each method, though, the simplest way would probably to employ aspect-oriented programming.
Actually, it sounds like this particular system would benefit from the employment of a code coverage documentation tool.
Note that in some IDEs, if you want to see who's calling a method, it's often as easy as a right-mouse click in the method source code. In Eclipse, for example, the right-mouse menu "References" submenu will do this.
Sometimes the only way things ever got fixed is because people became uncomfortable.