mirror of
https://github.com/SOCI/soci.git
synced 2026-02-15 02:38:42 -06:00
f032c2a695
Unfortunately we don't get any real information about these leaks, the
entire report is
==10667==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 176 byte(s) in 1 object(s) allocated from:
#0 0x7ff24b649602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7ff23f0ef551 (<unknown module>)
Indirect leak of 744 byte(s) in 3 object(s) allocated from:
#0 0x7ff24b649602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7ff23f0ef551 (<unknown module>)
Indirect leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7ff24b649602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602)
#1 0x7ff23f456d89 (<unknown module>)
So we can only disable leaks coming from libasan.so to suppress them
which, of course, risks hiding any other leaks too. The only way to
check for them is to check that the count of suppressions in libasan.so
doesn't increase beyond 5.