[LLVMbugs] [Bug 19948] new[]/delete mismatch

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=19948

Marco Antognini <antognini.marco at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Marco Antognini <antognini.marco at gmail.com> ---
It seems you're right! I did install llvm tools on Monday from the git repos
but the binary used by my test was not the correct one:

(lldb) target modules list 
[  0] 58839031-7790-349F-A2A5-3CD59C3DF9A2 0x0000000100000000 ./build/test 
[  1] 4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE 0x000000010002e000
/usr/lib/libc++.1.dylib 
[...]

I did a quick hack with `sudo ln -s
/usr/local/Cellar/llvm35/HEAD/lib/llvm-3.5/usr/lib/libc++.dylib .` and now I
get:

(lldb) target modules list
[  0] FF973F64-5939-3183-A0FE-4D0E134BA573 0x0000000100000000 ./build/test 
[  1] 042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A 0x00007fff5fc00000 /usr/lib/dyld 
[  2] 6973F7CB-02B5-3AE8-8792-9E9C50652528 0x0000000000000000
/usr/local/lib/llvm-3.5/usr/lib/libc++.1.dylib 
[...]
[ 37] 4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE 0x0000000000000000
/usr/lib/libc++.1.dylib 
[...]

So it seems both /usr/lib/libc++.1.dylib (from Apple's CLT I guess) and
/usr/local/lib/llvm-3.5/usr/lib/libc++.1.dylib are loaded. Running the test
shows no issue this time.

I close this issue then. But I've one question: is there a flag/option to tell
clang to use libc++ from /usr/local/lib/llvm-3.5/usr/lib/ and not from
/usr/lib?

*** This bug has been marked as a duplicate of bug 17379 ***

-- 
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/20140605/226d3752/attachment.html>