I've managed to pass sanitizer flags )) I will add something like that to travis-ci later
*** h1 0.1 debug|==19083==ERROR: AddressSanitizer: global-buffer-overflow on address 0x000000a8cda8 at pc 0x0000006efec0 bp 0x7ffc78cfc990 sp 0x7ffc78cfc988 *** h1 0.1 debug|READ of size 8 at 0x000000a8cda8 thread T0 *** h1 0.1 debug| #0 0x6efebf (/big/xxx/haproxy-travis-ci-fix/haproxy+0x6efebf) *** h1 0.1 debug| #1 0x7f7d969c0412 (/lib64/libc.so.6+0x24412) *** h1 0.1 debug| #2 0x42177d (/big/xxx/haproxy-travis-ci-fix/haproxy+0x42177d) *** h1 0.1 debug| *** h1 0.1 debug|0x000000a8cda8 is located 56 bytes to the left of global variable '__initcb_483' defined in 'src/task.c:483:1' (0xa8cde0) of size 8 *** h1 0.1 debug|0x000000a8cda8 is located 0 bytes to the right of global variable '__initcb_1692' defined in 'src/log.c:1692:1' (0xa8cda0) of size 8 *** h1 0.1 debug|SUMMARY: AddressSanitizer: global-buffer-overflow (/big/xxx/haproxy-travis-ci-fix/haproxy+0x6efebf) *** h1 0.1 debug|Shadow bytes around the buggy address: *** h1 0.1 debug| 0x000080149960: f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 *** h1 0.1 debug| 0x000080149970: f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 *** h1 0.1 debug| 0x000080149980: f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 *** h1 0.1 debug| 0x000080149990: f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 ср, 24 апр. 2019 г. в 17:51, Willy Tarreau <[email protected]>: > On Wed, Apr 24, 2019 at 04:03:24PM +0500, ???? ??????? wrote: > > I'm going to use various sanitizers, for example > CFLAGS="-fsanitize=address" > > I'm looking for preferred way to set additional CFLAGS, am I right that > it > > is something like ADDINC="-fsanitize=address" ? any other way ? > > I'm used to specifying them in CPU_CFLAGS which usually only contain the > optimization level and -march/-mcpu/-mtune. I find it more convenient this > way, especially since some settings depend on optimization level! > > Willy >
