Re: [PATCH] dump_stack() based on prologue code analysis

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 31 Jul 2006 11:15:50 +0200, Franck Bui-Huu <vagabon.xyz@xxxxxxxxx> wrote:
> > Yes, that is what I wanted.  Imagine if a exception happened on first
> > place on non-leaf function.  In this case, we must assume the function
> > is leaf since RA is not saved to the stack.
> 
> The only case I can imagine is when sp is corrupted which is unlikely.

Modern gcc somtimes do amazing optimization ;-)

> However an exception can occure just after a prologue of a nested
> function which is more likely. In that case you will assume wrongly
> that the function was a leaf one.

Why?  get_frame_info() should detect frame_size and pc_offset for that
case.

Is your objection against "info->func_size / 4" part?  the "4" comes
from size of a instruction.

Well, using "4" instead of "sizeof(union mips_instruction)" or
"sizeof(*ip)" was my old fault...

---
Atsushi Nemoto


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux