reiserfs on 2.4.1,2.4.2-pre (with null bytes patch) breaks mozilla compile
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)
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.
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'
So, there's something quite wrong here.
If anyone wants me to try something, do tell...
Cheers//Frank
Signature · 9 lines
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ [email protected] /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]Quoted 9 lines · On Saturday, February 17, 2001 05:21:18 PM +0100 Frank de Lange…
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.
Quoted 8 lines
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?
Quoted 7 lines
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
I can say "me too" for this. I thought it was perhaps glibc or binutils tho. I only have reiserfs systems now so I don't have a basis for comparison.
However I -can- say that I didn't experience this until I put glibc 2.2.1 on my systems. I do use an "approved" gcc, stock 2.95.2.
I wouldn't be so quick to pin it on reiserfs.
-d
Quoted 49 lines · Chris Mason
Quoted 9 lines · On Saturday, February 17, 2001 05:21:18 PM +0100 Frank de Lange…
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.
Quoted 8 lines
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?
Quoted 7 lines
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · David
I can say "me too" for this. I thought it was perhaps glibc or binutils tho. I only have reiserfs systems now so I don't have a basis for comparison.
However I -can- say that I didn't experience this until I put glibc 2.2.1 on my systems. I do use an "approved" gcc, stock 2.95.2.
I wouldn't be so quick to pin it on reiserfs.
Well, I run glibc-2.2.1 as well, so that might be one of the factors contributing to this. Then again, glibc-2.2.1 with ext2 does not cause any problems whatsoever with mozilla. So it could be that reiserfs + glibc-2.2.1 is a bad combination, question remains which of these two is the culprit (if not both). Since glibc-2.2.2 is out, I will give that a try as well. Not tonight though...
And no, I'm not running RedHat 7.x for those who might think so (and automatically blame everything on it).
When did you switch to glibc-2.2.1? Were you running reiserfs before that?
Cheers//Frank
Signature · 9 lines
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ [email protected] /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]Quoted 7 lines
Well, I run glibc-2.2.1 as well, so that might be one of the factors contributing to this. Then again, glibc-2.2.1 with ext2 does not cause any problems whatsoever with mozilla. So it could be that reiserfs + glibc-2.2.1 is a bad combination, question remains which of these two is the culprit (if not both). Since glibc-2.2.2 is out, I will give that a try as well. Not tonight though...
Quoted 6 lines
And no, I'm not running RedHat 7.x for those who might think so (and automatically blame everything on it).
When did you switch to glibc-2.2.1? Were you running reiserfs before that?
Cheers//Frank
Yes I was running reiserfs before 2.2.1 and I switched to 2.2.1 a couple months ago. Since then I've been dealing with issues. I've had to recompile half a dozen things similar to sendmail, apache etc. They segfaulted. It wasn't as purely backward compatible as expected.
I typically compile everything on one machine and distribute it. Thus far everything has been ok save a few issues I haven't been able to pin down. One of these issues is the inability to compile mozilla. Also related, I can't recompile gcc 2.95.2.
All of these things I was able to do just fine before the changeover. To note, I used to cvs up mozilla and recompile it every few days. I suppose I'll build an ext2 system and try things out.
Oh btw, I don't run That distribution either.
-d
Quoted 4 lines · On Sunday, February 18, 2001 03:07:27 AM +0100 Frank de Lange…
And no, I'm not running RedHat 7.x for those who might think so (and automatically blame everything on it).
Minor nit, but I'd rather clear it up now. Which distribution you run doesn't matter for debugging. What does matter is that we've got known problems with a given compiler, and that compiler goes by a few different flavors with the same version number. Since there are known problems, if you don't provide the compiler version, I'll ask. If your bug is *really* odd, I might ask a few different ways, just to make sure you give the same answer every time ;-)
-chris
Quoted 6 lines · David
Quoted 6 lines
Well, I run glibc-2.2.1 as well, so that might be one of the factors contributing to this. Then again, glibc-2.2.1 with ext2 does not cause any problems whatsoever with mozilla. So it could be that reiserfs + glibc-2.2.1 is a bad combination, question remains which of these two is the culprit (if not both). Since glibc-2.2.2 is out, I will give that a try as well. Not tonight though...
FYI
I'm running glibc-2.2.2 now, and alas... Mozilla still refuses to be compiled, no change...
Cheers//Frank
Signature · 9 lines
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ [email protected] /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]