While using trace messages from TraceUtil to find a problem with a codec, I discovered that in some cases there are multiple versions of functions (i.e. Algorithm_create in Algorithm_BIOS.c and in Algorithm_NoOS.c) which output identical messages (i.e. "ti.sdo.ce.alg.Algorithm - Algorithm_create> Enter(fxns=0xc3170, idma3Fxns=0x0, iresFxns=0xc3124, params=0x423c8d0c, attrs=0x423c8a6c)")
Because of this, you may always not be able to determine what code is being executing by examining the trace output. Most of the time you can, but sometimes, you'll have to go read the code. Of course, you never know which situation you're in!
I strongly recommend that the code be updated to uniquely identify the source of all trace messages. This could save significant amounts of time for developers.