From: Andi Kleen <ak@muc.de>
To: George Anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]Call frame debug info for 2.6 kernel
Date: Tue, 23 Mar 2004 03:04:10 +0100 [thread overview]
Message-ID: <m3n0685nfp.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1CHY0-1Uw-9@gated-at.bofh.it> (George Anzinger's message of "Tue, 23 Mar 2004 01:30:13 +0100")
George Anzinger <george@mvista.com> writes:
> This patch adds call frame debug record generation for entry.S frames.
[...]
Sorry, but that's quite ugly and will be hard to maintain (kinda like
maintaining an own assembler on your own) I think it would be far
better to require recent binutils for DEBUG_INFO builds and use the
.cfi_* mnemonics. They make dwarf2 code *much* simpler and cleaner.
Overall I think it's a good idea to add full dwarf2 annotation to
the i386 kernel, but not without assembler please.
-Andi
next parent reply other threads:[~2004-03-23 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1AR5s-75I-27@gated-at.bofh.it>
[not found] ` <1CHY0-1Uw-9@gated-at.bofh.it>
2004-03-23 2:04 ` Andi Kleen [this message]
2004-03-23 21:45 ` [PATCH]Call frame debug info for 2.6 kernel George Anzinger
2004-03-24 6:25 ` Andi Kleen
2004-03-24 16:20 ` George Anzinger
2004-03-17 21:37 Fixes for .cfi directives for x86_64 kgdb Jim Houston
2004-03-23 0:17 ` [PATCH]Call frame debug info for 2.6 kernel George Anzinger
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=m3n0685nfp.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.