games/freebsd-games larn

Peter Jeremy peterjeremy at
Fri Apr 27 10:16:38 UTC 2007

On 2007-Apr-26 14:18:17 -0700, Dima Ruban <dima at> wrote:
>> A little more information would be useful.  Running truss(1) on the
>> process running the game might tell you whether it did something naughty.

>write(1,"ignore\^[[20;1H\^[[M\^[[24;1H\^["...,31) = 31 (0x1f)
>ioctl(0,FIONREAD,0xbfbfea28)			 = 0 (0x0)
>read(0,"l",1)					 = 1 (0x1)
>write(1,"\^[[16;17H \^[[17;17H#\^[[24;1H"...,156) = 156 (0x9c)
>read(0,"r",1)					 = 1 (0x1)
>sigaction(SIGBUS,{ SIG_DFL SA_RESTART ss_t },{ 0x8058630 SA_RESTART ss_t }) = 0 (0x0)
>write(2,"\nLarn - Panic! Signal 10 receiv"...,42) = 42 (0x2a)
>nanosleep({2.000000000})			 = 0 (0x0)
>kill(28293,SIGBUS)				 = 0 (0x0)
>sigreturn(0xbfbfe700)				 ERR#134605842 'Unknown error: 134605842'
>Process stopped because of:  16
>process exit, rval = 10

This doesn't make a great deal of sense to me.  There's no sign of the
SIGBUS being delivered between the read() and sigaction().  The latter
is in sigpanic() and so must be after the SIGBUS was received.  There
are also two SIGBUS reports.  I suspect that truss is getting confused
and not reporting things in the correct temporal order.

Your best bet might be to capture a core file or run the code in a
debugger and try and get a backtrace.  This would at least give you
a pointer to where the SIGBUS is being generated.

Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list