search for: 0a360000

...(de)registerEH did not help. Looking at relocations and sections printouts, the exception is: Unhandled exception at 0x0A3600D1 : 0xC0000005: Access violation writing location 0x00BC7680. which is right after the start of .text: emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203 ... Resolving relocations Section #1 0A360000 so at least it is running code but tries to write a wrong location. Another run exhibits similar crash, still in .text but somewhat later. I have checked and the function address I'm running...

> err:module:load_builtin_dll failed to load .so lib for builtin L"dbghelp.dll": /usr/bin/../lib32/wine/dbghelp.dll.so: failed to map segment from shared object: Cannot allocate memory > err:module:load_builtin_dll failed to load .so lib for builtin L"dbghelp.dll": /usr/bin/../lib32/wine/dbghelp.dll.so: failed to map segment from shared object: Cannot allocate memory >

Jochen wrote: > > then I would imagine the problem is in the nvidia driver...yes? Now I > heard there were problems with the game and older dirvers, so I can not > go back to one to "fix" this problem--- any ideas? Then go forward. Newest driver version is 173.14.09. It does fix some problems.

...(de)registerEH did not help. Looking at relocations and sections printouts, the exception is: Unhandled exception at 0x0A3600D1 : 0xC0000005: Access violation writing location 0x00BC7680. which is right after the start of .text: emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203 ... Resolving relocations Section #1 0A360000 so at least it is running code but tries to write a wrong location. Another run exhibits similar crash, still in .text but somewhat later. I have checked and the function address I'm running...

...gt; > ** ** > > Unhandled exception at 0x0A3600D1 :**** > > 0xC0000005: Access violation writing location 0x00BC7680.**** > > ** ** > > which is right after the start of .text:**** > > ** ** > > emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: 0A360000 > DataSize: 253203 StubBufSize: 0 Allocate: 253203**** > > ...**** > > Resolving relocations Section #1 0A360000**** > > ** ** > > so at least it is running code but tries to write a wrong location.**** > > Another run exhibits similar crash, still in .text b...

...x0A3600D1 :**** >> >> 0xC0000005: Access violation writing location 0x00BC7680.**** >> >> ** ** >> >> which is right after the start of .text:**** >> >> ** ** >> >> emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: >> 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203**** >> >> ...**** >> >> Resolving relocations Section #1 0A360000**** >> >> ** ** >> >> so at least it is running code but tries to write a wrong location.**** >> >> Another run exhib...

...x0A3600D1 :**** >> >> 0xC0000005: Access violation writing location 0x00BC7680.**** >> >> ** ** >> >> which is right after the start of .text:**** >> >> ** ** >> >> emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: >> 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203**** >> >> ...**** >> >> Resolving relocations Section #1 0A360000**** >> >> ** ** >> >> so at least it is running code but tries to write a wrong location.**** >> >> Another run exhib...

...C0000005: Access violation writing location 0x00BC7680.**** >>> >>> ** ** >>> >>> which is right after the start of .text:**** >>> >>> ** ** >>> >>> emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: >>> 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203**** >>> >>> ...**** >>> >>> Resolving relocations Section #1 0A360000**** >>> >>> ** ** >>> >>> so at least it is running code but tries to write a wrong location.**** &gt...

...C0000005: Access violation writing location 0x00BC7680.**** >>> >>> ** ** >>> >>> which is right after the start of .text:**** >>> >>> ** ** >>> >>> emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: >>> 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203**** >>> >>> ...**** >>> >>> Resolving relocations Section #1 0A360000**** >>> >>> ** ** >>> >>> so at least it is running code but tries to write a wrong location.**** &gt...

...ocation 0x00BC7680.**** >>>> >>>> ** ** >>>> >>>> which is right after the start of .text:**** >>>> >>>> ** ** >>>> >>>> emitSection SectionID: 1 Name: .text obj addr: 0A3F1350 new addr: >>>> 0A360000 DataSize: 253203 StubBufSize: 0 Allocate: 253203**** >>>> >>>> ...**** >>>> >>>> Resolving relocations Section #1 0A360000**** >>>> >>>> ** ** >>>> >>>> so at least it is running code but tries to...

I would guess that it's crashing somewhere in the generated code. On Windows we don't have a way to get call stacks to the generated code (though if you want to try it on Linux, that should work). You can probably look at the address where the crash is occurring and verify that it is in the generated code. There are a couple of things I would look for. First, I'd take a look at the

OS is Windows 7 64 bit OS, compiler is 32 bit Visual C++ 2012 with 32 bit. The target which is i686-pc-mingw32-elf so I can use the ELF dynamic loader. Code model, relocation model and and memory manager are whatever default for this - did not modify. The Module comes from clang. The source is 1000 or more lines repeating C++ code in one big function: A+1; A*B.t(); where A and B are