NOTE: I havent put it in the above-post example, but it is POSSIBLE to put the
gettaskinfo INSIDE the debug function, but I cant remember the 'numbers'
required to achieve that. Its all to do with what numbers you enter into
the "num" parameter of the gettaskino...

From POOR memory, it goes something like this, just follow the logic...

gettaskinfo( ZERO ,name,NULL) will give you the name of the debug_function.
In my example this would be "debug_wait". Therefore using Zero is useless for our purposes.

gettaskinfo( ONE ,name,NULL) will give you the name of the function the as-yet un-executed wait is in.
In my example this would be the same as the string being passed into the debug_function.
Using this from inside the debug_function streamlines the macro a lot.

gettaskinfo( TWO ,name,NULL) will give you the name of the function that will be called AFTER
the as-yet un-executed wait is called. This has no parallel in my example.
This MAY be useful to you as I believe you wanted ORIGINALLY to know the NEXT function...


PS REMEMBER !!! "default.c" must NOT be included AT ALL or this whole system falls on its face!