malloc update problem? [maybe not]

walt wa1ter at
Thu Feb 9 16:59:03 PST 2006

I've been testing Kevin's malloc patch on -current, and I thought
that I had discovered a bug.

Now, I'm not so sure.

When building pkgsrc/lang/clisp I spotted an error message
during the 'configure' phase of the build:

checking for working mprotect... Bus error (core dumped)

Eventually I reverted the malloc.patch and did a make world just
to see if it fixed my error.

No -- I still see the same bus error in the same place  :o/

Here is my puzzle:  I see the coredump when I build clisp in
the usual manner by typing 'bmake' in the pkgsrc/lang/clisp
directory.  *But* if I run 'configure' directly from the
pkgsrc/lang/clisp/work/clisp-2.33.2/ directory, everything
works great:  no coredumps.

So --> newbie question:  why can't I find a 'foo.core' after I
see a 'core dumped' error message?  What happens to the core
that claims to be dumped -- but apparently is *not* dumped?

Any hints how to debug this kind of problem in the general case?


More information about the Bugs mailing list