search for: appverif

...did not show double deletes during debugging. Further more I managed to narrow it down to 2 function calls: // stupid code, but its just for triggering heap error auto func = llvm::Function::Create(...); if (func) func->eraseFromParent(); The erase from parent triggers the invalid heap. I used appverif.exe and gflags.exe (page heap checks) but they could not find anything. The Function::Create is just a wrapper for new Function(). I also traced into this call, but did not see anything weird. It returns a valid ptr. Somehow the ptr returned by the new seems to be broken. If i'm not mistaken th...

...g debugging. Further more > I managed to narrow it down to 2 function calls: > > // stupid code, but its just for triggering heap error > auto func = llvm::Function::Create(...); > if (func) func->eraseFromParent(); > > The erase from parent triggers the invalid heap. I used appverif.exe and > gflags.exe (page heap checks) but they could not find anything. > The Function::Create is just a wrapper for new Function(). I also traced > into this call, but did not see anything weird. It returns a valid ptr. > Somehow the ptr returned by the new seems to be broken. If i...

I recently upgraded from llvm 3.7.1 to a pre release of llvm (3.8.0rc2) in order to test some issues regarding bug 24233. After upgrading I starting to see heap corruption messages in vs 2015 sp1 when my program exits. "HEAP[ConsoleEngine.exe]: Invalid address specified to RtlValidateHeap( 0000000000290000, 0000000000318698 )" Initially I only got it in Release build. Debug build seems

...t;> I managed to narrow it down to 2 function calls: >> >> // stupid code, but its just for triggering heap error >> auto func = llvm::Function::Create(...); >> if (func) func->eraseFromParent(); >> >> The erase from parent triggers the invalid heap. I used appverif.exe and >> gflags.exe (page heap checks) but they could not find anything. >> The Function::Create is just a wrapper for new Function(). I also traced >> into this call, but did not see anything weird. It returns a valid ptr. >> Somehow the ptr returned by the new seems to b...

...ow it down to 2 function calls: >>> >>> // stupid code, but its just for triggering heap error >>> auto func = llvm::Function::Create(...); >>> if (func) func->eraseFromParent(); >>> >>> The erase from parent triggers the invalid heap. I used appverif.exe and >>> gflags.exe (page heap checks) but they could not find anything. >>> The Function::Create is just a wrapper for new Function(). I also traced >>> into this call, but did not see anything weird. It returns a valid ptr. >>> Somehow the ptr returned by th...