If you are still using CodeWarrior, you can enable profiler hooks
and then write your own implementations. This is a pretty hard-core
way to go but you can get a lot of mileage with the technique if you
have no other recourse.
I have done this in the past to solve various hard-to-find problems.
It is a stunningly useful technique.
Basic idea:
if you enable profiling, CW will emit a call to a function
upon entry and exit
of each routine. You can write your own versions of these routines,
which can do anything you want.
IIRC, the name of the function is passed as a parameter to the
routine (helpful, that!).
Best way to get all the info is to make a sample project, turn on
profiling, and then
disassemble the code from one file - look at the procedure entry and exit.
--
-- Marshall
It is by caffeine alone I set my mind in motion.
It is by the beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
