[Top] [All Lists]

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

Subject: Re: [PATCH] dump_stack() based on prologue code analysis
From: Atsushi Nemoto <>
Date: Mon, 31 Jul 2006 22:39:23 +0900 (JST)
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <>
On Mon, 31 Jul 2006 11:15:50 +0200, Franck Bui-Huu <> 
> > 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

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

<Prev in Thread] Current Thread [Next in Thread>