🚀 go-pugleaf

aep@world.std.com (Andrew E Page) writes:
 >   I'm working a on a significant body of someone elses code that I'm
 >translating to unix from the Mac and PC world.  
 >   Is there a function that can tell you the calling history of your
 >program?  


On a SUN OS 4.1 workstation here is what I do.  I define an include file
named where.h that contains:

#define WHERE(programnamestring)                                          \
{{{                                                                       \
   char buffer[512];                                                      \
   sprintf(buffer,"echo 'where ; detach' | dbx %s %d",                    \
                               programnamestring, getpid());              \
   system(buffer);                                                        \
}}}

and #include it in a module where I need traceback info.

Then I insert expansions of the form:

   WHERE("myprog");

where, "myprog" is the name of the executable program.  

This will invoke an external debugger (dbx) that will interact with the program
to create the traceback list whenever the expansion of WHERE() is executed.
The traceback will be written to stdout.
-- 
Larry Weiss, lfw@oc.com  
214/888-0471