> Yeah, try it without the -s option. Because -s works for me, too.
I can confirm that Windows states that the executables with debug
symbols (using the 20090619 build) are not valid images. If I
understand correctly then, libgcc_s_sjlj-1.dll is compiled with the
newer (post 20090606) binutils an
2009/6/22 Chris Sutcliffe :
>>> The dwarf build isn't that much necessary IIUC. Just take a typical
>>> mingw.org's 32-bit compiler and just update the binutils with current
>>> cvs-head version for it. I assume you will have the same issues here.
>>> All debug sections aren't loadable, and aren't
>> The dwarf build isn't that much necessary IIUC. Just take a typical
>> mingw.org's 32-bit compiler and just update the binutils with current
>> cvs-head version for it. I assume you will have the same issues here.
>> All debug sections aren't loadable, and aren't allocated, which is
>> here IMHO
> The dwarf build isn't that much necessary IIUC. Just take a typical
> mingw.org's 32-bit compiler and just update the binutils with current
> cvs-head version for it. I assume you will have the same issues here.
> All debug sections aren't loadable, and aren't allocated, which is
> here IMHO the
2009/6/22 Chris Sutcliffe :
>> Well, as I can see aren't those debugging sections marked as "LOAD".
>> But they have relocations, which means of course, that startup will
>> fail. Could you verify that this behaviour happens for i686-pc-mingw32
>> (for dwarf debugging) with new binutils, too?
>
> W
> Well, as I can see aren't those debugging sections marked as "LOAD".
> But they have relocations, which means of course, that startup will
> fail. Could you verify that this behaviour happens for i686-pc-mingw32
> (for dwarf debugging) with new binutils, too?
Where can I get a i686-pc-mingw32 Dw
2009/6/22 Kai Tietz :
> 2009/6/22 Chris Sutcliffe :
>>> A subsequent issue I found was that Windows complains that the
>>> libgcc_s_sjlj-1.dll in the 20090612 build is not a valid windows DLL.
>>> Reverting to the 20090606 automated build solved the problem.
>>
>> I noticed that the 20090612 build
2009/6/22 Chris Sutcliffe :
>> A subsequent issue I found was that Windows complains that the
>> libgcc_s_sjlj-1.dll in the 20090612 build is not a valid windows DLL.
>> Reverting to the 20090606 automated build solved the problem.
>
> I noticed that the 20090612 build are no longer listed so I tri
> A subsequent issue I found was that Windows complains that the
> libgcc_s_sjlj-1.dll in the 20090612 build is not a valid windows DLL.
> Reverting to the 20090606 automated build solved the problem.
I noticed that the 20090612 build are no longer listed so I tried the
20090619 build and experien
