hi all, is there a way to debug the performance of a constraint program without having to understand the implementation of the libraries that it uses? Using the trace utility I can see the constraints as they become active, but I can't tell what line of my code ultimately leads to each of the constraints, and so seeing them is of little value. What is your workflow when debugging programs for performance? Best, MishaReceived on Mon May 20 2013 - 22:49:20 CEST
This archive was generated by hypermail 2.2.0 : Wed Jun 12 2013 - 18:13:12 CEST