Is there a "civilised" (i.e. fairly portable and not to tricky to code) way that a procedure can find what's called it at runtime, without having to have gdb etc.?

The sort of scenario I'm looking at is "instrumenting" a database connection object's GetHandle() function, so that an atomic semaphore can log what's caused a critical section to be entered and an assertion can report details on attempts to reenter?