FreeBSD Port: bzflag-2.0.2

[Chuck Swiger]

On Apr 11, 2005, at 8:59 AM, TooManySecrets wrote:
> Can you help me, please?

Well, I'll try, but...

> pid 77253 (thunderbird-bin), uid 1001: exited on signal 11 (core 
> dumped)
> pid 11014 (firefox-bin), uid 1001: exited on signal 11 (core dumped)
> info: [drm] Loading R200 Microcode
> pid 88866 (firefox-bin), uid 1001: exited on signal 11 (core dumped)
> stray irq13
> info: [drm] Loading R200 Microcode
> pid 91935 (gconfd-2), uid 1001: exited on signal 6
> pid 60781 (conftest), uid 0: exited on signal 12 (core dumped)
> pid 75192 (typesconfig), uid 0: exited on signal 11 (core dumped)
> pid 75197 (typesconfig), uid 0: exited on signal 11 (core dumped)
> pid 30465 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 92003 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 76022 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 52265 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 45140 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 91501 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 15591 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 47691 (cintltst), uid 0: exited on signal 6 (core dumped)
> pid 58164 (cintltst), uid 0: exited on signal 6 (core dumped)

...this sure looks like a hardware problem, not a problem with the 
bzflag program specificly.  I'd double-check your cooling and make sure 
your CPU fan is okay, then try running memtest.org's checker overnight.

(The signal 6's could also be because you recompiled your system using 
excessive optimization or for the wrong CPU architecture, but the 
assortment of sig 11's and other signals suggests hardware failure.)

-- 
-Chuck