Re: Segfaults when compiling anything but 3.2-release

["STeve Andre'" <andres_(_at_)_msu_(_dot_)_edu>]

I'm willing to bet that your problem lies in something you did
with your kernel.  You are pretty much self-supporting when
you roll your own kernel, as weird and subtle things can happen
when you do this, and the developers can't tear their hair out
trying to figure out obscure problems in custom kernels.

I frequently run custom kernels, but I ALWAYS make a matching
generic kernel when compiling -current.  That way I can quickly
switch to generic if something odd happens.  And you know... there
has never been a time when something odd in the kernel hasn't
been *my* fault.  The defaults are the way they are for good
reasons.

Please try a generic kernel; if the problem persists get a
memory tester like memtest86 and test it really hard.

--STeve Andre'

On Monday 14 April 2003 10:27, Christopher Nehren wrote:
> I just recently installed OpenBSD on an old Pentium 150 with 32 MB RAM
> and an IBM 40 GB drive. I built my own kernel (with the help of the
> dmassage utility, which I highly recommend), and did a 'make build'
> after that. Being that this is a router box for my home network, I want
> it to be as secure as possible, so I checked out the 3.2-stable code
> from CVS. However, cc1 segfaults at various points during the build
> (Kerberos IV | V, libc, libc_r). I'd think it's a problem with the RAM,
> except that I haven't experienced any problems anywhere else in the
> system (I just did another kernel and world build last night / this
> morning after a clean install). I'd provide more information, but there
> really isn't anything that I can see which would be pertinent -- the
> build reaches a seemingly arbitrary spot, and then segfaults, with no
> other information.
>
> [demime 0.98d removed an attachment of type application/pgp-signature which
> had a name of signature.asc]