linux-mips
[Top] [All Lists]

Re: Saving arguments on the stack

To: "Knittel, Brian" <Brian.Knittel@powertv.com>
Subject: Re: Saving arguments on the stack
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 23 Nov 2005 09:54:35 +0000
Cc: linux-mips@linux-mips.org, Dominic Sweetman <dom@mips.com>
In-reply-to: <762C0A863A7674478671627FEAF5848105AF92D5@hqmail01.powertv.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <762C0A863A7674478671627FEAF5848105AF92D5@hqmail01.powertv.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
On Tue, Nov 22, 2005 at 10:24:09AM -0800, Knittel, Brian wrote:

> We'd like to add arguments to the backtrace in Oops messages to make
> debugging from these reports more efficient. It is particularly useful
> for determining where the problem was generated, particularly when bad
> pointers are passed in. This is for production embedded devices with
> optimized code and which reboot immediately after storing or sending the
> Oops message. Performance is an issue, but the overhead of storing the
> arguments on the stack is likely worth the added debug info.

In this case you would probably have to modify the compiler to save all
arguments.  Another issue is actually finding the stackframe.  For a
debugger using debug information this is possible but short of that it's
hard on MIPS to produce a meaningful backtrace.  Or having something
as complicate as on ia64 ...

  Ralf

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