Re: Trouble with ASan

2017-03-06 Thread coypu
On Sun, Mar 05, 2017 at 05:58:06PM +0100, Rhialto wrote: > On Tue 07 Feb 2017 at 21:40:21 +, co...@sdf.org wrote: > > I get the impression I should be compiling everything with asan, > > but it's unclear to me how to start to build all of netbsd this > > way. > > Which version of clang were yo

Re: Trouble with ASan

2017-03-05 Thread Rhialto
On Tue 07 Feb 2017 at 21:40:21 +, co...@sdf.org wrote: > I get the impression I should be compiling everything with asan, > but it's unclear to me how to start to build all of netbsd this > way. Which version of clang were you using? I have one from pkgsrc and it claims /usr/pkg/bin/clang -

Re: Trouble with ASan

2017-02-07 Thread coypu
Apparently as an alternative to preloading a separate ld.elf_so and others, I can disable ASLR. Still unsure what to do with the pthread stuff. I get the impression I should be compiling everything with asan, but it's unclear to me how to start to build all of netbsd this way.

Re: Trouble with ASan

2017-02-07 Thread coypu
On Tue, Feb 07, 2017 at 11:16:20AM +, co...@sdf.org wrote: > env LD_PRELOAD="/usr/amd64/ .. The crazy LD_PRELOAD command is because of this: ==15831==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING. ==15831==P

Trouble with ASan

2017-02-07 Thread coypu
Hi, I wanted to run our tests with asan/ubsan. I've used the following: cd /usr/src ./build.sh ... -O /usr/amd64 release cd /usr/src/lib/libm env USETOOLS=never CFLAGS="-fsanitize=undefined -fsanitize=address -U_FORTIFY_SOURCE" LDFLAGS="-lasan -pthread -lubsan" make -j20 cd /usr/tests/lib/libm