[llvm-bugs] [Bug 47881] New: DynamicLibraryTests fails on Windows when building with rpmalloc

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=47881

            Bug ID: 47881
           Summary: DynamicLibraryTests fails on Windows when building
                    with rpmalloc
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: hans at chromium.org
                CC: alexandre.ganea at ubisoft.com, htmldeveloper at gmail.com,
                    llvm-bugs at lists.llvm.org

cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=llvm
-DLLVM_USE_CRT_RELEASE=MT -DLLVM_INTEGRATED_CRT_ALLOC=\src\rpmalloc ..\llvm &&
ninja DynamicLibraryTests.exe &&
unittests\Support\DynamicLibrary\DynamicLibraryTests.exe && echo OKAY || echo
FAIL

Fails


cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=llvm
-DLLVM_USE_CRT_RELEASE=MT ..\llvm && ninja DynamicLibraryTests.exe &&
unittests\Support\DynamicLibrary\DynamicLibraryTests.exe && echo OKAY || echo
FAIL

Succeeds.


(Note that the tests themselves appear to succeed, but the binary doesn't exit
cleanly.)


Looking at DynamicLibraryTest and PipSqueek, it kind of makes sense. Objects
are getting passed across the main exe and the PipSqueek dll, and when building
with rpmalloc, those will have different heaps.

(Interestingly, lit didn't notice until
https://github.com/llvm/llvm-project/commit/338dd138ea4a70b52ab48e0c8aa38ec152b3569a
and I'm still not entirely sure why.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20201016/4e5b3b3b/attachment.html>