The Question is:
I am trying to track the source of a memory leak. I have successfully replaced
the decc$malloc, decc$calloc, decc$realloc, and decc$free routines by
replacing the c$alloc object file in the decc object library. I know my
application is not leaking the m
emory. I am using several shareable images the use
lib$get_vm,lib$free_vm,lib$vm_malloc, lib$vm_calloc, lib$vm_realloc, and
lib$vm_free for memory management. I want to replace these calls with my
custom memory allocator to determine which shareable ima
ge is leaking the memory. Is there a patch utility for the alpha to facilitate
The Answer is :
Your actions are unsupported and are certainly not recommended.
DO NOT REPLACE ANY OpenVMS LIBRARY COMPONENTS IN THIS FASHION.
Of course if you are used to programming on other platforms, this
wholesale replacement of system objects and this proposed
patch-based approach might seem perfectly reasonable. (On OpenVMS,
these are not, and can potentially destabilize your application
environment and can potentially even cause OpenVMS components and
layered products to fail or OpenVMS to crash.)
The OpenVMS Wizard would strongly encourage the use of the C
preprocessor for this purpose and variant-named entry points.
Please see topics (8411), (7876), (6870) and (3257) for related
Topics (7552) and (1661) have more general debugging information.