Date: Tue, 17 Jan 2006 16:06:33 +0900
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()
Message-ID: <20060117070633.GB10785@miraclelinux.com>
References: <20060116121611.GA539@miraclelinux.com> <20060116121834.GD539@miraclelinux.com> <1137422221.3034.25.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1137422221.3034.25.camel@laptopd505.fenrus.org>
User-Agent: Mutt/1.5.9i
From: mita@miraclelinux.com (Akinobu Mita)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 908
Lines: 20

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...
> 

I still cannot understand the importance of symbolsize in print_symbol()
very well. When is the decoder going bonkers for example?
Isn't it the task for kallsyms itself to detect that bonkers?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/