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?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
