On Jun 4, 2009, at 5:53 PM, Robert Covington wrote:

> I need a way to fathom what function is calling any other function  
> in my program.

The Xcode debugger lays out the entire calling chain and keeps it  
current. I've been able to run the Xcode debugger in 10.4 via Xcode  
2.5 with marginal success but it works fine in Leopard. I haven't  
tried to install Xcode 3.x ( and not sure if it works on Tiger ) on  
10.4.x

Regardless, an external monitoring program ( like the Xcode debugger )  
is typically easier than trying to write code within the app to  
monitor itself. The FBtoC C runtime provides nothing out of the box in  
the way of data about the calling chain and it's hard to imagine how  
it could be successful since at least some functions ( particularly in  
the C runtime ) are called via an address in a pointer instead of  
directly by function name. An external monitor simply watches  
everything that is called.

It might be possible to write an internal monitor but the effort would  
be non-trivial and debatable given the existing functionality of the  
Xcode debugger.

Brian S.