On Wed, Jun 14, 2000 at 03:26:57PM -0700, Adam J. Richter wrote:
> I have upgraded our bin86 from 0.4 to 0.14.9 because lilo 21.4.4
> contains some as86 source code that now uses the .asciz pseudo-op. This
> has exposed a bug in as86-0.14.9.
>
> If you tell as86-0.14.9 to generate a program listing, it
> will do writes of a negative size, due to a pointer being null when
> it does not expect this to be the case. The Linux terminal and /dev/null
> drivers silently ignore these writes, but the ext2 filesystem (at
> least in 2.4.0test1-ac18) interprets the length as unsigned and generates
> a "file size limit exceeded" signal.
>
> When this happens, linebuf points to some valid data.
> You shoudl be able to reproduce this problem by attempting to
> build dosemu 1.0.0. Here is an excerpt from the build log:
>
> gcc -E -D__AS86__ --traditional -I../include fossil.S > fossil.s
> as86 -l -0 -o fossil.o fossil.s > fossil.s.out
Please send me fossil.s.
H.J.
