From owner-freebsd-current@FreeBSD.ORG Sun Oct 5 00:47:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7705C106568F for ; Sun, 5 Oct 2008 00:47:48 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 504BA8FC1A for ; Sun, 5 Oct 2008 00:47:48 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [192.168.0.2] (p53.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m950lhtv057029; Sat, 4 Oct 2008 17:47:47 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <48E80F02.4070309@freebsd.org> Date: Sat, 04 Oct 2008 17:49:06 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jos@catnook.com References: <20081004080511.GA72641@lizzy.catnook.local> <20081004161024.GA67323@nagual.pp.ru> <20081004222249.GA48928@lizzy.catnook.local> In-Reply-To: <20081004222249.GA48928@lizzy.catnook.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrey Chernov , freebsd-current@freebsd.org Subject: Re: firefox3-bin crashes near arc4random_buf() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2008 00:47:48 -0000 Jos Backus wrote: >>On Sat, Oct 04, 2008 at 01:05:11AM -0700, Jos Backus wrote: >> >>>For a few weeks now firefox3-bin has been crashing semi-regularly for me. >>>Backtrace attached. I selected `Build a debugging image' but the resulting >>>binary is stripped, so no symbols. >>>#3 0x28237381 in XRE_InitEmbedding () from /usr/local/lib/firefox3/libxul.so >>>#4 >>>#5 0x2a39eb2d in arc4random_buf () from /lib/libc.so.7 > > A few weeks ago, after these crashes had started happening, I rebuilt most > ports on this machine, hoping it would fix the issue, but it has not. > > Any suggestions on how to debug this? First, you need to share the first items in the backtrace, as they're more likely to be correct. I agree with Andrey that it looks like there's some stack corruption, so it's hard to trust anything except the first couple of entries. You should also look at several independent core dumps and see how much the backtraces have in common. It might also be worth running it under ktrace, forcing the crash, then sharing the last few dozen lines from kdump output. Good luck, Tim Kientzle