We've released new versions of both our Lock Inversion Detector, LID and our Lock Inversion Analyser, LIA today.
This release fixes a problem when running LIA against an executable which has been compiled with Frame Pointer Omission enabled. This causes some call stacks to be reported as zero length and we were failing to treat these correctly which led to a vast number of duplicate lock sequences being created. Also a bug has been fixed in LIA which caused it to fail to use symbol paths supplied on the command line when looking up symbols.
We've also added several new command line switches to LIA to enable you to ignore inversions that occur in specific dlls, limit the number of lock inversions reported, ignore stack frames which are shorter than a configurable length and force slower but more reliable call stack collection to be used.
All customers are being contacted via email with details of how to obtain the latest release of LIA and you can download the latest version of LID from here (if you've already registered for the updates mailing list then simply reply to the email notification and we'll send you the latest version).
Do continue to get in touch with comments and suggestions and any problems that you have.
Leave a comment