Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 13 Mar 2003 20:02:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 13 Mar 2003 20:00:50 -0500 Received: from [12.36.124.2] ([12.36.124.2]:16331 "EHLO intranet.resilience.com") by vger.kernel.org with ESMTP id ; Thu, 13 Mar 2003 19:57:48 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Thu, 13 Mar 2003 17:08:26 -0800 To: Linus Torvalds , Horst von Brand From: Jonathan Lundell Subject: Re: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63)) Cc: "Randy.Dunlap" , Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 22 At 3:24pm -0800 3/13/03, Linus Torvalds wrote: >On Thu, 13 Mar 2003, Horst von Brand wrote: >> >> No need. Just dump some bytes before EIP raw, plus raw bytes + decoded >> after EIP. Could be of some help. > >Alpha does this. Of course, there you don't have any of the partial >instruction issues. If you've got a symbol some reasonable distance before EIP, you could decode from there. I wrote a little code that does that (using kallsyms) very crudely in the stack trace in order to give the reader a hint about stack frames. Go to the prior symbol, which is usually an entry point, and find the %esp arithmetic. Works pretty well for figuring out the real call chain. -- /Jonathan Lundell. - 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/