[LLVMdev] JIT Leaks?

[Anton Korobeynikov]

Hello, Paolo.

> I hope this is usefull, I'm pretty new to OS X.
Well. From your example you have got the only valgrind results:

==28336== 58 bytes in 2 blocks are possibly lost in loss record 70 of
127
==28336==    at 0x4020A92: operator new(unsigned)
(in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==28336==    by 0x410010B: std::string::_Rep::_S_create(unsigned,
unsigned, std::allocator<char> const&)
(in /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6.0.3)
==28336==    by 0x4102A04:
(within /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6.0.3)
==28336==    by 0x4102B25: std::string::string(char const*,
std::allocator<char> const&)
(in /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6.0.3)
==28336==    by 0x85530D6:
__static_initialization_and_destruction_0(int, int)
(MachineFunction.cpp:40)
==28336==    by 0x855311D:
_GLOBAL__I__ZN4llvm19MachineFunctionPass6virtfnEv
(MachineFunction.cpp:484)
==28336==    by 0x86E1A37:
(within /home/asl/proj/llvm/build_debug/Debug/examples/JITLeak)
==28336==    by 0x8355D50:
(within /home/asl/proj/llvm/build_debug/Debug/examples/JITLeak)
==28336==    by 0x86E197A: __libc_csu_init
(in /home/asl/proj/llvm/build_debug/Debug/examples/JITLeak)
==28336==    by 0x418E7F3: (below main) (in /lib/libc-2.5.so)

-- 
With best regards, Anton Korobeynikov.

Faculty of Mathematics & Mechanics, Saint Petersburg State University.