Am Donnerstag, den 23.11.2006, 10:20 -0800 schrieb Jurij Smakov:

> No problem :-). I'm still somewhat confused though. Do I understand 
> correctly that if you use the klibc utils and library from the 
> archive, it segfaults *only* when you run fstype on your /dev/hda4 
> (but runs ok on other partitions)? 

No, basically the main problem has nothing to do with partitions. It's
just that _none_ of the debian supplied klibc-utils work (not even a
simple one like /usr/lib/klibc/bin/true), because they immediately
segfault. I tried to track down the problem, but due to my limited
knowledge of linux/klibc internals i can only suspect that something
goes wrong the moment /lib/klibc-gZY_j4EiGiPMbozhciEvacptnN8.so is being
loaded and/or initialized. 
Versions used: libklibc-1.4.30-1, klibc-utils-1.4.30-1


What I then tried to do is to compile klibc myself, once for sparc and
then for sparc64.

** First try: sparc (32 bit) **

I unpacked the klibc package, set a link to the linux source tree,
linked linux/include/asm to linux/include/asm-sparc and typed
"KLIBCARCH=sparc make".
Then I tried to run the generated files under usr/utils/shared resp.
usr/utils/static (the shared ones inside a chroot so that they would
access the right klibc-*.so). 

I found out the following:
- the progs in usr/utils/static work fine
- the progs in usr/utils/shared all segfault, just as the ones supplied
by the debian packages


** Second try: sparc64 (64 bit) **

Now I unpacked klibc another time, but this time I linked
linux/include/asm to linux/include/asm-sparc64 and just typed "make".

Result:
- the progs in usr/utils/static work fine
- the progs in usr/utils/shared also work (this time using a 64 bit
klibc-cNP3iUE1BbKETtRZwHq6UJ7ssis.so)


Bottom line: The shared library gets loaded and initialized correctly
when built for sparc64, but not for sparc...


> If that's the case, can you please 
> build the klibc with debugging symbols and run gdb on it, to see where 
> fstype segfaults in that case? Alternatively, you can provide first 
> two kilobytes of /dev/hda4 using something like

Concerning the problem with the unrecognised ext3 partition I will file
a new bug report against klibc-utils.

cu,
Tomas




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to