On 01/30/2013 12:29 PM, Stephane Eranian wrote: > Will, > > Ok got rid of the double close. should be limited > to perfmon_int_wrap.c now. But that one is automatically > generated, so there is not much I can do about it. > > Thanks.
Hi Stephane, libpfm coverity report looks pretty good at this point. There isn't much that can be done about the automatically generated wrapper code. -Will > > > On Wed, Jan 30, 2013 at 6:00 PM, William Cohen <wco...@redhat.com> wrote: >> On 01/30/2013 10:58 AM, Stephane Eranian wrote: >>> Will, >>> >>> I have made a couple of changes based on the report. >>> Found a couple of bugs, so that was useful though it >>> is hard to parse the output even with the dictionary. >>> I think this comes from the fact that it prints the >>> steps in the simulation that led to a detected error. >>> >>> Thanks. >> >> Hi Stephan, >> >> Yes, sometime it is a slog through the output of coverity because of all the >> output related to how it figured out there was a problem. Generally, I read >> the top of the error message to see what the error is and then skip to >> bottom to see where it is flagged. >> >> >> The results look a bit better in the new libpfm git version. Attached are >> the results for the current git tree. >> >> -Will ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
