From owner-freebsd-ports Wed Apr 24 20:50:53 2002 Delivered-To: freebsd-ports@freebsd.org Received: from gyros.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by hub.freebsd.org (Postfix) with ESMTP id 6DFE437B405 for ; Wed, 24 Apr 2002 20:50:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by gyros.marcuscom.com (8.12.3/8.12.3) with ESMTP id g3P3lBt9026495; Wed, 24 Apr 2002 23:47:11 -0400 (EDT) (envelope-from marcus@marcuscom.com) Subject: Re: FreeBSD Port Mozilla - fails badly when I ran portupgrade From: Joe Marcus Clarke To: Sean Chittenden Cc: Chip Wiegand , ports@FreeBSD.ORG In-Reply-To: <20020424201320.A82196@ninja1.internal> References: <20020423231838.60e8f150.chip@wiegand.org> <20020423232253.D61911@ninja1.internal> <1019675885.8815.46.camel@gyros.marcuscom.com> <20020424145609.O61911@ninja1.internal> <1019703039.297.12.camel@gyros.marcuscom.com> <20020424201320.A82196@ninja1.internal> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 25 Apr 2002 00:47:11 -0300 Message-Id: <1019706431.26338.11.camel@gyros.marcuscom.com> Mime-Version: 1.0 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 2002-04-25 at 00:13, Sean Chittenden wrote: > > This might be an issue with library incompatibilities or a missing > > lib. > > Possible. It used to work with .9.7, upgraded to 0.9.9 and it didn't > work, same fate with rc1. > > > However, you should be able to get a core dump by making sure the > > following sysctl variables are set, and the coredumpsize ulimit is > > non-zero: > > > > kern.sugid_coredump: 1 > > kern.coredump: 1 > > $ su > Password: > 8:07pm sean@mat:/etc # sysctl kern.suid_coredump=1 > sysctl: unknown oid 'kern.suid_coredump' > 8:08pm sean@mat:/etc # sysctl kern.sugid_coredump=1 > kern.sugid_coredump: 0 -> 1 > 8:08pm sean@mat:/etc # sysctl kern.coredump=1 > kern.coredump: 1 -> 1 > 8:08pm sean@mat:/etc # limits > Resource limits (current): > cputime infinity secs > filesize infinity kb > datasize 524288 kb > stacksize 65536 kb > coredumpsize infinity kb > memoryuse infinity kb > memorylocked infinity kb > maxprocesses 7302 > openfiles 14605 > sbsize infinity bytes > 8:08pm sean@mat:/etc # exit > 8:08pm sean@mat:/etc > mozilla > Segmentation fault > 8:08pm sean@mat:/etc > > > And syslog logs the following: > Apr 24 20:09:40 mat /kernel: pid 1656 (mozilla-bin), uid 1000: exited on signal 11 Can you try running mozilla from a directory you have write permissions on? Of course, without debugging symbols, the core analysis might not do any good. > > Other ideas on how to get it to leave a trace? -sc > Another option is to tie gdb to the running mozilla process: gdb /usr/X11R6/lib/mozilla/mozilla-bin Then get mozilla to crash. Joe > -- > Sean Chittenden > -- PGP Key: http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message