From: mita@miraclelinux.com (Akinobu Mita)
To: Arjan van de Ven <arjan@infradead.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] omit symbol size field in print_symbol()
Date: Tue, 17 Jan 2006 00:51:53 +0900 [thread overview]
Message-ID: <20060116155153.GA6628@miraclelinux.com> (raw)
In-Reply-To: <1137422221.3034.25.camel@laptopd505.fenrus.org>
On Mon, Jan 16, 2006 at 03:37:01PM +0100, Arjan van de Ven wrote:
> On Mon, 2006-01-16 at 21:18 +0900, Akinobu Mita wrote:
> > I can't find useful usage for the symbol size in print_symbol().
> > And symbolsize seems to be fixed when vmlinux or modules are compiled.
> > So we can calculate it from vmlinux or modules.
>
>
> the use is that you can see if the EIP actually is inside the function,
> or if the decoder is going bonkers. Quite useful feature that...
>
If it is really useful, should we have it on x86-64 too?
The patches 1/3 and 2/3 will do that.
Andi Kleen doesn't want because The call trace on x86-64 could have more
than one symbol per line, but my patches will print more characters than
now.
next prev parent reply other threads:[~2006-01-16 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:16 [PATCH 0/3] changes about Call Trace: Akinobu Mita
2006-01-16 12:17 ` [PATCH 1/3] makes print_symbol() return int Akinobu Mita
2006-01-16 14:16 ` Jesper Juhl
2006-01-16 14:24 ` Akinobu Mita
2006-01-16 15:18 ` Jesper Juhl
2006-01-16 12:18 ` [PATCH 2/3] use usual call trace format on x86-64 Akinobu Mita
2006-01-16 12:22 ` Andi Kleen
2006-01-16 12:32 ` Christoph Hellwig
2006-01-16 12:46 ` Andi Kleen
2006-01-16 12:18 ` [PATCH 3/3] omit symbol size field in print_symbol() Akinobu Mita
2006-01-16 12:22 ` Andi Kleen
2006-01-16 14:37 ` Arjan van de Ven
2006-01-16 15:51 ` Akinobu Mita [this message]
2006-01-17 7:06 ` Akinobu Mita
2006-01-16 12:22 ` [PATCH 0/3] changes about Call Trace: Andi Kleen
2006-01-16 13:41 ` Akinobu Mita
2006-01-16 13:41 ` Akinobu Mita
2006-01-16 13:42 ` Akinobu Mita
2006-01-16 22:22 ` Andi Kleen
2006-01-17 16:53 ` Jan Engelhardt
2006-01-17 7:05 ` Akinobu Mita
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=20060116155153.GA6628@miraclelinux.com \
--to=mita@miraclelinux.com \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox