From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: When issuing an ls or mkdir command a segmentation fault results. All other commands seem to be working. Recently performed up2date on all components. Will try booting to an earlier kernel. Version-Release number of selected component (if applicable): kernel 2.4.20-13.7 How reproducible: Always Steps to Reproduce: 1.ls 2. 3. Actual Results: segmentation fault Expected Results: directory listing Additional info: same happens with mkdir command
See if 'dmesg' says anything interesting.
Dmesg did not produce any clues as to what may be causing this.
Please show me the output of this command: rpm -q '%{arch}\n' glibc; uname -a
package %{arch}\n is not installed glibc-2.2.4-32
Sorry, gave the wrong command. Please try this: rpm -q --qf '%{arch}\n' glibc uname -a
result of the above command i686
..and 'uname -a'?
rpm -q --qf '%{arch}\n' uname -a produced no result. Returned to the command prompt.
sorry about that <<uname -a>> produced the output Linux domainname.com 2.4.20-13.7 date....i686 unknown
Run 'gdb ls' and at the (gdb) prompt type 'r' and press return. When you get a segmentation fault, type 'bt' and press return. What does it say?
#0 0x8503fff in strcpy() at strcpy:-1 #1-#6 same as above with hex shift #7 0x40044657 in__libc_start_main (main=08x049740<strcpy+568> argc=1, ubp_av=0xbfffeee4, init=0x8049060 <_inti>, fini=0x804fcb0 <_fini>, rtld_fini=0x4000dcd4 <_dl_fini>,stack_end 0xbfffeedc) at ../sysdeps/generic/libc-start.c:129 (gdb)
Do you get output from this command?: rpm -V fileutils glibc Also, did you try booting an earlier kernel?
rpm -V fileutils glibc produced list of executables in /bin directory. example S.5.... /bin/ls and one listing S.5... T c /etc/profile.d/colorls.sh Tried an earlier Kernel with the same results.
'S.5.... /bin/ls' as output is bad news: it means that the ls binary does not match the one that was installed from the fileutils package. Sounds like that binary was modified outside of the process of installing RPMs. Might want to check your security settings if this machine is on the Internet. (You could force upgrade the fileutils package to get the right binary back.)