[llvm-commits] [llvm] r99400 - in /llvm/trunk: lib/CodeGen/LiveIntervalAnalysis.cpp test/CodeGen/Generic/2010-03-24-liveintervalleak.ll

Török Edwin edwintorok at gmail.com
Wed Mar 24 15:00:44 PDT 2010


On 03/24/2010 11:22 PM, Bob Wilson wrote:
> On Mar 24, 2010, at 1:58 PM, Török Edwin wrote:
> 
>> On 03/24/2010 10:24 PM, Bob Wilson wrote:
>>
>> Could you give me some more details on which configuration this breaks?
>> Did it happen when running the test-suite with llvm-gcc or clang?
>> Did llc crash, or did valgrind show an error?
> 
> I was afraid you were going to ask that....  Oh well, it's good for me
> to figure out how these things work!  I poked around on the buildbot and
> found the error. 

Thanks!
BTW why didn't the buildbot email me? :)

> llc crashed with the following:
> 
> llc(1164) malloc: *** error for object 0x1041219c0: pointer being freed
> was not allocated
> *** set a breakpoint in malloc_error_break to debug
> 0  llc               0x00000001008fd932 PrintStackTrace(void*) + 34
> 1  llc               0x00000001008fe11e SignalHandler(int) + 622
> 2  libSystem.B.dylib 0x00007fff82898eaa _sigtramp + 26
> 3  libSystem.B.dylib 0x00007fff5fbfea98 _sigtramp + 3711327240
> 4  libSystem.B.dylib 0x00007fff8283f155 free + 128
> 5  llc               0x00000001005a1301
> llvm::LiveIntervals::releaseMemory() + 161

Ok that obviously matches what my patch did.

> 6  llc               0x0000000100886635
> llvm::PMDataManager::freePass(llvm::Pass*, llvm::StringRef,
> llvm::PassDebuggingString) + 117
> 7  llc               0x0000000100886bdc
> llvm::PMDataManager::removeDeadPasses(llvm::Pass*, llvm::StringRef,
> llvm::PassDebuggingString) + 172
> 8  llc               0x00000001008873c8
> llvm::FPPassManager::runOnFunction(llvm::Function&) + 280
> 9  llc               0x00000001008876db
> llvm::FunctionPassManagerImpl::run(llvm::Function&) + 139
> 10 llc               0x0000000100887916
> llvm::FunctionPassManager::run(llvm::Function&) + 102
> 11 llc               0x0000000100039d38 main + 3672
> 12 llc               0x00000001000385a8 start + 52
> 13 llc               0x0000000000000009 start + 4294736533
> 
> This was running with llvm-gcc.

I'll see if I can reproduce it tomorrow. Can you also tell me exactly
what revision the buildbot has built? (was it exactly mine or something
a bit later?)

>  I'd send you the bitcode file except
> that it has already been overwritten.  Is that good enough to help you
> figure it out?

Hope so, if I can't reproduce I'll let you know.

Best regards,
--Edwin



More information about the llvm-commits mailing list