Fluid <[EMAIL PROTECTED]> wrote:
> How about signal 4? I was rebuilding my -current the other day and I
> kept getting mostly signal 4 errors (in different places) with a couple
> of signal 10's and 11's. I tried finding a run-down of what the various
> errors meant, but I couldn't find a thing.
The signal number mapping is in /usr/include/sys/signal.h.
[ Um, if you don't know what the signals mean, you might not want to be
running -current. ]
SIGILL (signal 4) is usually not good (e.g., bad RAM, IDE data
> The weird thing is that when
> I switched terminals in KDE (i.e. opened a new Konsole window), my build
> problems ceased.
Possible bad RAM: the new window allocated enough memory such that
a bad spot in memory was allocated to the new Konsole's process, and not
randomly to the build processes.
> Windows XP runs on the same box with no problems (i.e.
> will run for weeks without a reboot) so I'm a little hesitant to blame
> my hardware.
This doesn't necessarily mean much. Windows will either not stress
the hardware as much, or will use RAM in different ways. I seem to
recall hearing rumors that Windows allocates memory from the top down.
If so, and if FreeBSD allocates memory from the bottom up (I don't
know), that could explain why you do not appear to be seeing the problem
However, as other people are having mysterious problems with
-current, it could be a software problem.
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message