bus error

Joshua Oreman oremanj at webserver.get-linux.org
Wed Jun 25 15:46:38 PDT 2003


On Wed, Jun 25, 2003 at 05:49:30PM -0400 or thereabouts, David S. Jackson wrote:
> Joshua Oreman suggested I try "bt" while in gdb looking at the
> core files.  The output from that command was:
> 
> for vim.core:
> 
> #0  0x2815a26b in memset () from /usr/libexec/ld-elf.so.1
> Cannot access memory at address 0xbfbfe6e0.
> 
> for xinit.core:
> #0  0x2805826b in memset () from /usr/libexec/ld-elf.so.1
> Cannot access memory at address 0xbfbfe6bc.

As I feared. If you've got the developer mentality, forge ahead.
If not, forget about it :-)

You have to recompile those programs with debugging flags.
make configure the port, take a look at the software Makefile
(the one in work/<portname>-<portversion>/), and look for a
line that starts with CFLAGS=. Add ` -g' (without the quotes, of
course), to the end. Run make inside the software directory
(/usr/ports/<category>/<port>/work/<port>-<portversion>/).
Take the newly produced executable (it should be either in the
directory you ran 'make' in, or one of the subdirectories) and
run it under gdb (gdb myexecutable). Type `run' at the gdb prompt.
When it crashes, type `bt'. Send us the output :-)

> 
> There is no /etc/malloc.conf file.  Should there be?

It's okay the way it is.

-- Josh

> 
> [Sorry about not including the post--I had to get this off the
> archives, since I tried Earthlink's Spaminator, and it deleted
> everything from freebsd.org....  Oops.]
> 
> -- 
> David S. Jackson                        dsj at dsj.net
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> I was in Vegas last week. I was at the roulette table,
> having a lengthy argument about what I considered an
> Odd number.  -- Steven Wright


More information about the freebsd-questions mailing list