Displaying 5 results from an estimated 5 matches for "consoleengin".
Did you mean:
consoleengine
2016 Feb 24
2
Heap problems with 3.8.0rc2 in combination with vs2015 sp1
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 to be fine, but
recently I also got them in Debug build.
I traced it down how to trigger it in Debug Mode. It happens when I put the
Execution...
2016 Feb 25
0
Heap problems with 3.8.0rc2 in combination with vs2015 sp1
...r <gekkekoe at gmail.com> wrote:
>
> 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 to be fine,
> but recently I also got them in Debug build.
> I traced it down how to trigger it in Debug Mode. It happens...
2016 Feb 25
2
Heap problems with 3.8.0rc2 in combination with vs2015 sp1
...gt; wrote:
>
>>
>> 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 to be fine,
>> but recently I also got them in Debug build.
>> I traced it down how to trigger it in Deb...
2016 Feb 25
0
Heap problems with 3.8.0rc2 in combination with vs2015 sp1
...throws heap error. During debug when I force HasHungOffUses = true,
everything is fine and the correct original ptr is computed and freed. So
I'm guessing that that value should have stayed true.
I also have set a data breakpoint on HashHungOffUses when it's accessed and
did noticed that
ConsoleEngine.exe!llvm::Function::__autoclassinit2(unsigned __int64) C++
ConsoleEngine.exe!llvm::Function::Create(llvm::FunctionType * Ty,
llvm::GlobalValue::LinkageTypes Linkage, const llvm::Twine & N,
llvm::Module * M) Line 116 C++
caused it to be set to False. So do I need to trace into all the Function...
2016 Feb 26
2
Heap problems with 3.8.0rc2 in combination with vs2015 sp1
...ug when I force HasHungOffUses = true,
> everything is fine and the correct original ptr is computed and freed. So
> I'm guessing that that value should have stayed true.
>
> I also have set a data breakpoint on HashHungOffUses when it's accessed
> and did noticed that
> ConsoleEngine.exe!llvm::Function::__autoclassinit2(unsigned __int64) C++
> ConsoleEngine.exe!llvm::Function::Create(llvm::FunctionType * Ty,
> llvm::GlobalValue::LinkageTypes Linkage, const llvm::Twine & N,
> llvm::Module * M) Line 116 C++
>
> caused it to be set to False. So do I need to tra...