Date: Mon, 3 Nov 2003 15:20:11 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Lowell Gilbert <freebsd-stable-local@be-well.no-ip.com> Cc: stable@freebsd.org Subject: Re: exited on signal 11 on unrar Message-ID: <20031103152011.GA21305@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <44oevtinfm.fsf@be-well.ilk.org> References: <003e01c3a1fb$dc2b6300$4b28a8c0@its.setec.fr> <44oevtinfm.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 03, 2003 at 08:36:29AM -0500, Lowell Gilbert wrote: > "Adrien FACHE" <adrien.fache@its.setec.fr> writes: >=20 > > This is my first experiencing with writing to English-speaking > > mailing list, so, please excuse me for possible mistakes. > >=20 > > I'm a newbie on freebsd. I have a mail server on FreeBSD 4.7 with > > Postfix and Amavis ( mail virus scanner ). > >=20 > > The problem is I got this in my log periodically : > >=20 > > /kernel: pid 24499 (unrar), uid 1010: exited on signal 11 (core dumped) > >=20 > > I use unrar for Amavis=20 > >=20 > > Does this look like a software or hardware problem?=20 >=20 > http://www.freebsd-fr.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html= #SIGNAL11 If the OP had a hardware problem, then the crashes would occur randomly in any application and probably the kernel too (in which case the machine would panic). Even so, the observed symptoms might still be due to hardware problems, but given the circumstances I'd be thinking otherwise. If the problem always occurs in unrar(1) then either the unrar program on that machine is somewhat corrupted or you've discovered a bug in unrar. In the first case, simply reinstalling unrar will probably sort our the problem. Use cvsup(1) to pull down the latest ports tree and compile and install unrar from source. Before building, disable any excessive optimization levels you may have in /etc/make.conf -- certainly nothing more highly optimized than 'CFLAGS=3D -O -pipe'. Make sure CPUTYPE is either left unset or set to the correct type that matches your hardware. If the problem still persists, can you identify one or more attachments that cause unrar to SEGV repeatably, and possibly obtain a core dump from an unrar compiled with debugging symbols? unrar should never dump core, even when presented with pathological input, and the unrar developers (http://www.rarsoft.com/) will be most interested to hear about a repeatable way of making it do so. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/pnIrdtESqEQa7a0RAkyfAJ91BOdd6PfVUekWkLv0CVlehhCdJgCfWxS/ fIr/XfgD52c4hRu7B3CQwhc= =Pyqc -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031103152011.GA21305>