Adding CI with Sanitizers

[ax3l]

Hi,

are you planning to add CI to the PMIx repo?

One build could include a build and run with -fsanitize=address in order to avoid introducing memory leaks and violations in updates.

[jjhursey]

PR #1265 is re-enabling the -fsanitize=address version in the Travis config:

• https://github.com/openpmix/openpmix/blob/master/.travis.yml#L32-L36

We need community help on plugging the rest of the leaks to get it to pass.

[ax3l]

Little note: my PR is not re-enabling them, but enabling them for the first time ;) I just added these lines already as comments when adding CI in the first place.

Unfortunately, your best chance to get the leaks fixed is to sit down with the original authors of the affected routines. As someone (community) not familiar with the code base, I personally tried several times to get some of them resolved but one needs quite some deep understanding of the business logic to get this patched up initially.

[rhc54]

@ax3l I finally got around to doing this in the code base, enabling the "picky" compiler options and adding the sanitize=address option. Even got it all to build and work on my Mac.

However, when trying to get it thru CI, I ran into problems with compilers that support that sanitize option, but appear to require the addition of another library (believe it might be -lasan?). I'm having trouble finding the correct autoconf code to locate that library.

Any suggestions?