gus@Shasta.ARPA (Gus Fernandez) (05/31/86)
> The solution is simple: Use MacroScope to: > 1.) prowl the source code files that make up a program to produce a text file > containing the calling tree of the entire program (a graph of what calls > what for the entire program.) > 2.) resolve the calling graph against the linker source file to discover > what calling chains might potentially cause problems due to heap shuffling > and un-locked pointers. > 3.) examine the actual calls to determine whether the arguments are locked > or not. (Throw out those lines where it is easy to tell that all the > arguments are non-moveable.) > 4.) produce an error message file containing only those lines that might > cause problems. > > Unfortunately MacroScope hasn't been released for sale yet. > > --- David Phillip Oster -- "The goal of Computer Science is to > Arpa: oster@lapis.berkeley.edu -- build something that will last at > Uucp: ucbvax!ucblapis!oster -- least until we've finished building it." OK, you let the cat out of the bag. What's MacroScope (beyond what I can infer from the blurb above. Gus Fernandez