https://sourceware.org/bugzilla/show_bug.cgi?id=30448
--- Comment #10 from Tom Kacvinsky <tkacvins at gmail dot com> --- The problem is an access violation at startup, deep in the guts of the DLL loader. Doing a debug session with Visual Studio and looking at registers and memory locations, it was determined that loading the DLL in question is where things went south. And, for what it's worth, perhaps --disable-reloc-section is not a good name for an option - the DLL I produced with that option does have a .reloc section. So what exactly does --disable-reloc-section mean if specifying that option still results in a DLL with a .reloc section? -- You are receiving this mail because: You are on the CC list for the bug.
