This would aid in tracking down memory
heap corruptions, and would make it easier to
get the debugger of your choice to skip to the
next entrance to or exit from a subroutine.
When you invoke the VAX C compiler with -p for
profiling it generates an assembly-language call
to a profiling subroutine for which I substituted
my own heap-checker, and that enabled me to zero in
on a heap-violation which was caused by an array-
out-of-bounds condition.
--dave