Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262197AbTKCTcT (ORCPT ); Mon, 3 Nov 2003 14:32:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262592AbTKCTcT (ORCPT ); Mon, 3 Nov 2003 14:32:19 -0500 Received: from natsmtp01.rzone.de ([81.169.145.166]:57051 "EHLO natsmtp01.rzone.de") by vger.kernel.org with ESMTP id S262197AbTKCTcR (ORCPT ); Mon, 3 Nov 2003 14:32:17 -0500 Message-ID: <3FA6AD3E.5090706@softhome.net> Date: Mon, 03 Nov 2003 20:32:14 +0100 From: "Ihar 'Philips' Filipau" Organization: Home Sweet Home User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030927 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linux Kernel Mailing List Subject: Re: How provoke call stack trace References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1169 Lines: 33 Thanks to every one! Already looking into the source code. P.S. But it looks like ppc (as of 2.4.22) doesn't implement it. But still BUG() on ppc prints stack trace... I'm just no specialist in cpu exception handling. especially on ppc :-( Ihar 'Philips' Filipau wrote: > Hello All! > > [ Simple question. Probably FAQ - but I cannot find it. ] > > How can I print call stack trace, just like BUG() does? > But without asm(".long 0") as BUG() does. > > Is there any function which can be used by module to just investigate > some given call path? > -- Ihar 'Philips' Filipau / with best regards from Saarbruecken. -- _ _ _ "... and for $64000 question, could you get yourself |_|*|_| vaguely familiar with the notion of on-topic posting?" |_|_|*| -- Al Viro @ LKML |*|*|*| - 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/