From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 86E67DDDFD for ; Thu, 13 Sep 2007 01:57:57 +1000 (EST) In-Reply-To: <0D968216-6743-498E-9723-F029FF3746C1@kernel.crashing.org> References: <4948353cd5e9c566a8151eca8c4bbcb7@kernel.crashing.org> <0D968216-6743-498E-9723-F029FF3746C1@kernel.crashing.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <536DDC0F-E665-4C50-AB75-AE9DBDB8820D@kernel.crashing.org> From: Kumar Gala Subject: Re: still using stabs debug format? Date: Wed, 12 Sep 2007 11:00:32 -0500 To: bje@air.net.au, Ulrich Weigand Cc: "linuxppc-dev@ozlabs.org list" , Paul Mackerras , Ed Swarthout List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ben, Uli Paul/BenH suggested that you might be able to help with my question. > On Aug 17, 2007, at 7:54 PM, Segher Boessenkool wrote: > >>> Is anyone really still using the stabs format for kernel debug? >>> >>> can we kill off the .stabs references? >> >> What, you want to replace them with dwarf markup? Or just >> get rid of the debug info completely? > > There are two users today: > > * N_SO for file information we can easily make into .file > * N_FUN used in _GLOBAL() that marks it a 'function' is a bit > misleading since we use this for both functions and data. Not sure > what to do about that one, any suggestions? #define _GLOBAL(n) \ .text; \ .stabs __stringify(n:F-1),N_FUN,0,0,n;\ .globl n; \ n: this is the .stabs reference I'm trying to figure out what the dwarf equiv would be. - k