From: Peter Z. <ze...@li...> - 2001-06-30 06:55:18
|
On Sat, 30 Jun 2001 01:17:57 -0500 (CDT) Mumit Khan <khan@NanoTech.Wisc.EDU> wrote: > Yes, gcc runs ld to link. The GNU compilers create assembly output, and > then invokes the assembler to assemble to .o file and then the linker if > appropriate to create the final executable. > > The bug in question is in the Win9x C runtime fseek routine, which doesn't > zero out the area skipped over, and you get random garbage, which may > indeed be parts of virtual memory contents. I had a fix for it a long time > ago, but I don't know if that is used in the current binutils. However, the > "workaround" is not quite appropriate for the GNU source tree since it's > a platform specific hack. > > Regards, > Mumit I see, so it's treating this skipped over area as a null terminated string (which isn't null terminated on windows)? If you still have the patch around, any chance you could apply it to the next binary release? I know it's not your fault, but it's not exactly elegant to dump 1-2k of garbage to the final exe's :) -- Peter Zelezny. <ze...@li...> |