The return of ASAN issues

[Friedrich W. H. Kossebau]

Hi,

Am Montag, 30. Mai 2016, 19:42:38 CEST schrieb Ben Cooksley:
> As you may recall, some time ago the CI scripts were adapted to
> forcibly inject ASAN into all test processes launched on the CI system
> to fix Marble's tests, as Marble does not use ECM and thus does not
> enable ASAN as a result.
> 
> Unfortunately this has bad effects with certain processes,
> particularly Java based ones. This causes the tests of other projects
> to fail as a result with segmentation faults, as they're incompatible
> with forced ASAN injection - they have to actually be built with ASAN
> for it to work.
> 
> Can someone please investigate another solution?
> 
> As ASAN is contagious, I would suggest that any Framework which is
> compiled using ASAN have adjustments made to it's *Config.cmake files
> to ensure linking for any binary/library built with it is setup
> properly. I've no idea how complicated that is to setup though.

It is not just "Framework" as in "KF5", but any lib (built on CI) which uses 
KDECompilerSettings.cmake (or ECMEnableSanitizers.cmake directly) and is used 
by other KDE projects (which includes even Phonon), right?

Cheers
Friedrich