Re: [PATCH 3/3] omit symbol size field in print_symbol()

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 0/3] changes about Call Trace:
  - From: [email protected] (Akinobu Mita)
- [PATCH 3/3] omit symbol size field in print_symbol()
  - From: [email protected] (Akinobu Mita)
- Re: [PATCH 3/3] omit symbol size field in print_symbol()
  - From: Arjan van de Ven <[email protected]>

Prev by Date: Re: [PATCH 0/3] changes about Call Trace:
Next by Date: Re: RT question : softirq and minimal user RT priority
Previous by thread: Re: [PATCH 3/3] omit symbol size field in print_symbol()
Next by thread: Re: [PATCH 0/3] changes about Call Trace:
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]