RTC requires the standard heap management routines have wrapper/implementation interfaces, i.e. the wrapper functions can call the implementation(private) functions but not other wrapper functions. This limitation is used to avoid rtc internal memory map locking problem. The basic RTC api and coding examples can be found in the man page of rtc_api.
We are working on removing the internal memory map locking limitation. Before this is done, the wrapper/implementation method is still required. -Leonard Glenn Fowler wrote On 05/24/06 02:22,: >I feel like I'm monitoring secret RTC society traffic ... > >can someone just spell out what RTC requires of > malloc() > realloc() > free() >in user code > >ast already has macro hooks to associate __FILE__ __LINE__ __FUNCTION__ >with each vmalloc/malloc/calloc/strdup allocation/free/resize > >the hooks are enabled by nmake --debug-symbols ( i.e. CCFLAGS=-g ) >and enabled at runtime by export VMDEBUG > >the hooks essentially make the caller __FILE__ __LINE__ __FUNCTION__ >available to the underlying vmalloc allocation method/discipline > >if I deciphered this thread correctly one would just need to add >RTC instrumentation callouts to the underlying method/discipline > >-- Glenn Fowler -- AT&T Research, Florham Park NJ -- > > >
