日志文件只有AddressSanitizer报告，而没有LeakSanitizer报告。
默认情况下，AddressSanitizer在出错时会中止。LeakSanitizer只在exit上运行，因为你的程序不是exit，所以你不会得到泄漏报告。
下面是一个同时存在内存泄漏和缓冲区溢出的示例程序：

#include <malloc.h>

void *alloc(size_t sz) { return malloc(sz); }
void fn(char *p, int n) { p[n] = '\0'; }

int main()
{
  const int sz = 10;
  fn(alloc(sz), sz);

  return 0;
}

如果我用clang -g -fsanitize=address leaky.c -o leaky构建它，然后用ASAN_OPTIONS=detect_leaks=1运行它，我只会得到错误报告：

=================================================================
==1130841==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000001a at pc 0x5555a7f31f0f bp 0x7ffc86de9420 sp 0x7ffc86de9418
WRITE of size 1 at 0x60200000001a thread T0
    #0 0x5555a7f31f0e in fn /tmp/leaky.c:4:32
    #1 0x5555a7f31f4c in main /tmp/leaky.c:9:3
...
==1130841==ABORTING     <<<=== Note this.

This answer展示了如何使程序在出错时 * 不 * 中止。当我这样做时，我同时得到AddressSanitizer和LeakSanitizer报告：

clang -g -fsanitize=address -fsanitize-recover=address leaky.c -o leaky
ASAN_OPTIONS=detect_leaks=1:halt_on_error=0 ./leaky

=================================================================
==1131013==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000001a at pc 0x560f9d467f0f bp 0x7ffef258d2b0 sp 0x7ffef258d2a8
WRITE of size 1 at 0x60200000001a thread T0
    #0 0x560f9d467f0e in fn /tmp/leaky.c:4:32
    #1 0x560f9d467f5c in main /tmp/leaky.c:9:3
...
=================================================================
==1131013==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 10 byte(s) in 1 object(s) allocated from:
    #0 0x560f9d42d14e in __interceptor_malloc (/tmp/leaky+0xa314e) (BuildId: d2d081353c37b4b7a8659b1ac39242cfe6259078)
    #1 0x560f9d467eb4 in alloc /tmp/leaky.c:3:33
    #2 0x560f9d467f4f in main /tmp/leaky.c:9:6
    #3 0x7fbf2cc29209 in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16

SUMMARY: AddressSanitizer: 10 byte(s) leaked in 1 allocation(s).