Date: Fri, 27 Apr 2007 20:16:27 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Dima Ruban <dima@rdy.com> Cc: ports@freebsd.org, Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> Subject: Re: games/freebsd-games larn Message-ID: <20070427101627.GA840@turion.vk2pj.dyndns.org> In-Reply-To: <20070426211817.GA28242@sivka.rdy.com> References: <20070426043928.GA29793@sivka.rdy.com> <448xcfm9ib.fsf@Lowell-Desk.lan> <20070426164723.GA1835@sivka.rdy.com> <44irbikgw2.fsf@be-well.ilk.org> <20070426205000.GA27996@sivka.rdy.com> <44abwukfla.fsf@be-well.ilk.org> <20070426211817.GA28242@sivka.rdy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2007-Apr-26 14:18:17 -0700, Dima Ruban <dima@rdy.com> 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.
>
>Attached.
=2E..
>write(1,"ignore\^[[20;1H\^[[M\^[[24;1H\^["...,31) =3D 31 (0x1f)
>ioctl(0,FIONREAD,0xbfbfea28) =3D 0 (0x0)
>read(0,"l",1) =3D 1 (0x1)
>write(1,"\^[[16;17H \^[[17;17H#\^[[24;1H"...,156) =3D 156 (0x9c)
>read(0,"r",1) =3D 1 (0x1)
>sigaction(SIGBUS,{ SIG_DFL SA_RESTART ss_t },{ 0x8058630 SA_RESTART ss_t }=
) =3D 0 (0x0)
>write(2,"\nLarn - Panic! Signal 10 receiv"...,42) =3D 42 (0x2a)
>nanosleep({2.000000000}) =3D 0 (0x0)
=2E..
>kill(28293,SIGBUS) =3D 0 (0x0)
>sigreturn(0xbfbfe700) ERR#134605842 'Unknown error: 134605842'
>SIGNAL 10 (SIGBUS)
>SIGNAL 10 (SIGBUS)
>Process stopped because of: 16
>process exit, rval =3D 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.
--=20
Peter Jeremy
--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFGMc17/opHv/APuIcRAqThAJ0btUmfzA9KienKmLq8dLrgbhHaHgCfTkGM
Ffaz9hFagw+0TRnIQQckoXs=
=EvyI
-----END PGP SIGNATURE-----
--AhhlLboLdkugWU4S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070427101627.GA840>