bus error

David S. Jackson deepbsd at earthlink.net
Mon Jun 23 11:03:40 PDT 2003


I'm afraid I'm getting a nasty error when I try to do some very
fundamental things. Not sure what's back of all the problems.

For example when I try to start vim or even xinit, I get:

Jun 23 12:00:12 juno /kernel: pid 2700 (vim), uid 0: exited on signal 10


(I happened to be root at the time, but same applies to any user.)


When I try to startx, I get:

Bus error

uname -a shows: FreeBSD juno.dsj.net 4.5-STABLE FreeBSD
4.5-STABLE #7: Sun Apr 28 15:23:53 EDT 2002:
root at juno.dsj.net:/usr/src/sys/compile/JUNO i386

I do find .core files for proggies I cannot start, though. I went gdb vim vim.core and got the following:

***snip***
(no debugging symbols found)
Core was generated by 'vim'.
Program terminated with signal 10, Bus error.
Reading symbo9ls from /usr/X11R6/lib/libgtk12.so.2...
(no debugging symbols found)...done
Reading symbols from /usr/X11R6/lib/libgdk12.so.2...
(no debugging symbols found)...done
Reading symbols from /usr/X11R6/lib/libgmodule12.so.3...
(no debugging symbols found)...done
Reading symbols from /usr/X11R6/lib/libglib12.so.3...
(no debugging symbols found)...done
Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2...
(no debugging symbols found)...done
Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done
#0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1
(gdb)

***snip***

Here's the same thing for xinit.core

***snip***
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
Core was generated by 'xinit'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/X11R6/lib/libXmu.so.6...
(no debugging symbols found)...
Reading symbols from /usr/X11R6/lib/libXt.so.6...
(no debugging symbols found)...
Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done
#0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1
(gdb)

***snip***


Mind you, I typed this while looking at the screen of the other
box. Hope I got it correctly.

Any idea what is back of this?

Does it look like some file corruption to ld-elf.so.1?  How the
heck do I fix that if so? I tried to remake a kernel a while back
and couldn't even complete that process. (sniff, sniff)

What type of stuff uses ld-elf.so.1 anyway? Everything?

TIA.

-- 
David S. Jackson                        dsj at dsj.net
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I never forget a face, but in your case I'll make
an exception.
		-- Groucho Marx


More information about the freebsd-questions mailing list