I applied a Trace on function (method) in the RootCause GUI, but I don see it being called in the output. Why?
Here are some possibilities: • The function was called so often that it was load shed, and calls stopped being recorded. Click on the LOAD_SHED node at the end of your Trace Display, choose Show Associated Table, and look for your function there. Using the option-menu in the first column can designate the function as Do Not Shed for subsequent runs. • The function was called, but it’s not shown in the data file you’re viewing. Use Add Data Files to Display in the File menu to add earlier files. If you still don’t find it, then the data containing the last call may have been overwritten (i.e., the “trace buffer wrapped around”). You can save all data files containing the trace of a function by adding a SNAPSHOT probe ON_ENTRY to the function in the Trace Setup dialog. • There are multiple instances of the method in different classes, and you chose the wrong one. Use Find in Trace Setup and set traces on others that occur. The following possibilities apply only to native (C/C++) function
Related Questions
- How do I control a communication method to control the voice volume? What will happen to the switch and communication function operated in the COMBO example?
- I applied a Trace on function (method) in the RootCause GUI, but I don see it being called in the output. Why?
- What is the function of the record output selector?
