On 8 Mar 2009 at 22:42, basile wrote: > > hmm, that used to be ok, can you try 2.19.x just in case? > > > > > Okay tested vanilla binutils-2.19.1 Same behaviour. > > I'll test hardened 2.6.28 tomorrow. Too tired tonight.
no worries, i already reproduced it with latest PaX and everything and debugged it a bit. it's the early decompressor phase that somehow manages to overwrite itself as well and that causes an invalid opcode and further exceptions when the decompressor tries to print out a message (the putstr() code happens to be destroyed by then). this is likely due to some code underestimating the needed size of the decompressed stream, but i don't yet know why it's config dependent and whether it's some linker issue or a bug in PaX.
