https://sourceware.org/bugzilla/show_bug.cgi?id=17184
--- Comment #1 from mity at morous dot org --- I understand this kind of bug won't have big priority for most people working on binutils. Hence, I am willing to work on patch which would address this. I can see two paths forward: (1) 1st path would be to output more paddings between the resources, at least around the app. manifest as my experiments show the bug can be suppressed this way. This is partly based on observation that RC.EXE from MSVC inserts much more paddings into the .rsrc section. The patch would not be much intrusive, but there would be danger it fixes only my instance of the bug. (2) Follow much closer the layout as output either by RC.EXE, or by a program using Windows API to output resources (BeginUpdateResource() & al.) The patch (or rather a patch series) would have to be more intrusive. The resource tree is streamed out in quite different order by RC.EXE then it is with windres.exe. This should, in long term, provide quite good guaranty of survive in the mine field of subtle incompatibility bugs as this one. I would welcome some feedback which way is preferred by binutils maintainers. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
