Closed stefanbeller closed 11 years ago
The reason for this is, that I have currently no means of checking if a given trace file was really generated with a given binary. As soon as I figure something out, I will look into this.
fixed on two different levels. the main cause for this was an error in the addr_translate code, where it would segfault if debug information was found for function name, but not for file name, which in turn was caused by the wrong binary being provided for a given trace. both of which are fixed in develop for review.
(tested on the 0.5 tarball version from your website)
When just linking to the graprof library, but forgetting to enable "-g -finstrument-functions" I get a crash of graprof.