From: Kumar Gala <galak@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Ed Swarthout <Ed.Swarthout@freescale.com>
Subject: Re: still using stabs debug format?
Date: Sat, 18 Aug 2007 11:33:31 -0500 [thread overview]
Message-ID: <0D968216-6743-498E-9723-F029FF3746C1@kernel.crashing.org> (raw)
In-Reply-To: <4948353cd5e9c566a8151eca8c4bbcb7@kernel.crashing.org>
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?
- k
next prev parent reply other threads:[~2007-08-18 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 13:17 still using stabs debug format? Kumar Gala
2007-08-18 0:54 ` Segher Boessenkool
2007-08-18 16:33 ` Kumar Gala [this message]
2007-09-12 16:00 ` Kumar Gala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D968216-6743-498E-9723-F029FF3746C1@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Ed.Swarthout@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox