From owner-freebsd-current@FreeBSD.ORG Tue Jun 20 10:08:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE42416A474 for ; Tue, 20 Jun 2006 10:08:02 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F52E43D46 for ; Tue, 20 Jun 2006 10:07:58 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k5KA7qoC034971; Tue, 20 Jun 2006 14:07:52 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k5KA7lhZ034962; Tue, 20 Jun 2006 14:07:47 +0400 (MSD) (envelope-from yar) Date: Tue, 20 Jun 2006 14:07:46 +0400 From: Yar Tikhiy To: "Andrew R. Reiter" Message-ID: <20060620100746.GO23729@comp.chem.msu.su> References: <20060618192011.GF715@turion.vk2pj.dyndns.org> <20060618152428.A36995@fledge.watson.org> <20060619184540.GJ23729@comp.chem.msu.su> <20060619190822.GE966@turion.vk2pj.dyndns.org> <20060619221550.GM23729@comp.chem.msu.su> <20060619181929.W40529@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060619181929.W40529@fledge.watson.org> User-Agent: Mutt/1.5.9i Cc: Peter Jeremy , current@freebsd.org Subject: Re: NULL pointer dereference panic 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: Tue, 20 Jun 2006 10:08:02 -0000 On Mon, Jun 19, 2006 at 06:20:54PM -0400, Andrew R. Reiter wrote: > On Tue, 20 Jun 2006, Yar Tikhiy wrote: > :On Tue, Jun 20, 2006 at 05:08:22AM +1000, Peter Jeremy wrote: > :> On Mon, 2006-Jun-19 22:45:41 +0400, Yar Tikhiy wrote: > :> >Peter, what gcc options did you build the kernel with? My question > :> >is unrelated to the panic, I'd just like to make stack traces look > :> >sane in common cases :-) > :> > :> In /etc/make.conf: > :> CPUTYPE?=athlon-xp > :> CFLAGS=-O -pipe > :> COPTFLAGS=-O -pipe > : > :Indeed, gcc in athlon-xp mode handles function calls in a manner > :different from the i386 default one. The old backtrace would be > :confused, too, by the code generated so. > : [...] > > Thanks for the information regarding athlon-xp. Have other OSes done > anything (special casing?) for this hardware so as to make it more easy > for "better" traces to be done? I think the only reliable way of determining the number of arguments to a function, particularly in the athlon-xp code from gcc, is to use debugging symbols. However, that would require loading the full symbols along with kernel and module files. We can leave it to kgdb for now, it's really good at it. -- Yar