Interpreted Expressions

TotalView sets a breakpoint in your code and executes the evaluation point. Since TotalView is executing the expression, interpreted expressions run slower (and possibly much slower) than compiled expressions. With multiprocess programs, interpreted expressions run even more slowly because processes may need to wait for TotalView to execute the expression.

When you are debugging remote programs, interpreted expressions always run more slowly because TotalView on the host, not the TotalView debugger server (tvdsvr) on the client, executes the expression. For example, an interpreted expression could require that 100 remote processes wait for the TotalView debugger process on the host machine to evaluate one interpreted expression. In contrast, if TotalView compiles the expression, it is evaluated on each remote process.

If the expression contains $stop, TotalView stops evaluating the expression and stops the process when it executes the $stop intrinsic.

Note:   Whenever a thread hits an interpreted patch point, TotalView stops execution. This means that TotalView will create a new set of lockstep groups. Consequently, if goal threads contain interpreted patches, the results are unpredictable.