Displaying 4 results from an estimated 4 matches for "mdmalloc".
Did you mean:
dmalloc
2007 Jul 15
2
[LLVMdev] JIT Leaks?
...00 0x00000000 0x00000000
0x01102a58 ............X*..
Leak: 0x01103610 size=16
0x00000000 0x00000000 0x00000000
0x01103368 ............h3..
So all I know is that It's a size 16 leak *grin*.
But MallocDebug reports as leaks
2.4M start
2.4M operator new(unsigned long)
2.4M MDmalloc
2.4M main
2.4M llvm::PMDataManager::add(llvm::Pass*, bool)
2.4M llvm::LoopPass::assignPassManager(llvm::PMStack&,
llvm::PassManagerType)
2.4M llvm::LLVMTargetMachine::addPassesToEmitMachineCode
(llvm::FunctionPassManager&, llvm::MachineCodeEmitter&, bool)
2.4M llvm::JIT::JIT[in-charg...
2007 Jul 15
0
[LLVMdev] JIT Leaks?
........X*..
> Leak: 0x01103610 size=16
> 0x00000000 0x00000000 0x00000000
> 0x01103368 ............h3..
>
> So all I know is that It's a size 16 leak *grin*.
>
> But MallocDebug reports as leaks
>
> 2.4M start
> 2.4M operator new(unsigned long)
> 2.4M MDmalloc
> 2.4M main
> 2.4M llvm::PMDataManager::add(llvm::Pass*, bool)
> 2.4M llvm::LoopPass::assignPassManager(llvm::PMStack&,
> llvm::PassManagerType)
> 2.4M llvm::LLVMTargetMachine::addPassesToEmitMachineCode
> (llvm::FunctionPassManager&, llvm::MachineCodeEmitter&, bool)
&...
2007 Jul 14
0
[LLVMdev] JIT Leaks?
On 2007-07-14, at 13:56, Anton Korobeynikov wrote:
>> You can find out what exactly leaks with the help of valgrind.
>
> It seems, that Paolo is on Mac OS X. No valgrind there :(
All is not lost…
http://developer.apple.com/documentation/Performance/Conceptual/
ManagingMemory/Articles/FindingLeaks.html
— Gordon
2007 Jul 14
4
[LLVMdev] JIT Leaks?
Holger.
> You can find out what exactly leaks with the help of valgrind.
It seems, that Paolo is on Mac OS X. No valgrind there :(
--
With best regards, Anton Korobeynikov.
Faculty of Mathematics & Mechanics, Saint Petersburg State University.