I'm curious if there is some way, perhaps with some directive or something to force a debug backtrace to happen, but without an error. I have a function that is getting called twice and should only be called once, so my thought is that if I could go into the routine and put something there that outputs a backtrace.. same as when there is an error in the program.. where it shows the entire list of calls, but not because of an error.. then it would continue to run and I could see the entire chain that resulted in the call each time. I know there are other ways I can find this, but the issue made me wonder if there was a way I could ask for my own backtrace with a command inside the program Because that would be a quick easy way to find all the call chains that get to this function.. And it would be cool to be able to do such a thing, especially on large Complicated projects. James
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal