Bug ID: 41494
           Summary: New leak in OpenMP library
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Runtime Library

This is with git master / svn trunk of openmp runtime.
The backtrace is:
==31833==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 120 byte(s) in 1 object(s) allocated from:
    #0 0x5ad35d in malloc
    #1 0xbf620f in ___kmp_allocate_align(unsigned long, unsigned long)
    #2 0xbf0572 in ___kmp_allocate
    #3 0xc1faac in __kmp_register_root
    #4 0xc1b8dc in __kmp_do_serial_initialize()
    #5 0xc19058 in __kmp_get_global_thread_id_reg
    #6 0xba3f08 in __kmpc_global_thread_num
    #7 0x5ec089 in main
    #8 0x7f8c9135409a in __libc_start_main

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

It first appeared roughly a month ago, but i only now looked into it..
It's very unfortunate, as this is the only leak from the library,
AND for it to be detected the openmp library itself doesn't need to be built
with asan/lsan,
only the program that uses -fopenmp needs to be built with asan/lsan.
Meaning it's really noisy.

You are receiving this mail because:
You are on the CC list for the bug.
llvm-bugs mailing list

Reply via email to