Re: reiserfs on 2.4.1,2.4.2-pre (with null bytes patch) breaks mozilla compile

[Chris Mason <mason@suse.com>]

On Saturday, February 17, 2001 05:21:18 PM +0100 Frank de Lange
<frank@unternet.org> wrote:

> Hi'all,
> 
> Well, subject says it all... When I try to compile mozilla (CVS version)
> with the '--enable-elf-dynstr-gc' option, the compile fails with a
> segfault:
> 
> ../../dist/bin/elf-dynstr-gc ../../dist/lib/components/libsample.so
> make[2]: *** [install] Segmentation fault (core dumped)
> 

That's not good.  Which compiler did you use to compile the kernel?  This
sounds lame, but reiserfs exercises the cpu/mem more than ext2, so we hit
bad ram more often.  If we run out of other things to try, please run a
memory tester.

> compiling the same codebase on an ext2 filesystem does not produce this
> segfault. When I compare the produced library (libsample.so), there is a
> consistent difference between the one compile on the reiserfs and the ext2
> filesystem. Running objdump on the reiserfs-compiled library also produces
> errors (some assertion failures, a lot of 'invalid string offset' errors,
> and finally a 'Memory exhausted' error), while objdump happily
> disassebles the ext-produced binary.
> 

Where in the libsample.so file are the differences (what byte offset?).
Are they restricted to a given range, or do they vary randomly?

> These problems occur on:
> 
>  2.4.1
>  2.4.2-pre4
>  2.4.2-pre4 with Chris Mason's 'reiserfs fix for null bytes in small
>  files'
> 
At least the patch didn't make it worse.  Would anyone care to comment on
how the elf-dynstr-gc option changes the file access patterns for the
compile?

thanks,
Chris