Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 13 Mar 2003 23:18:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 13 Mar 2003 23:18:20 -0500 Received: from air-2.osdl.org ([65.172.181.6]:58247 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Thu, 13 Mar 2003 23:18:19 -0500 Message-ID: <33130.4.64.238.61.1047616146.squirrel@www.osdl.org> Date: Thu, 13 Mar 2003 20:29:06 -0800 (PST) Subject: Re: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63)) From: "Randy.Dunlap" To: In-Reply-To: References: X-Priority: 3 Importance: Normal Cc: , , , X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 28 > 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. as long as it's not a data symbol... can you determine that? ~Randy - 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/