Message-ID: <3FA6AD3E.5090706@softhome.net>
Date: Mon, 03 Nov 2003 20:32:14 +0100
From: "Ihar 'Philips' Filipau" <filia@softhome.net>
Organization: Home Sweet Home
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030927
MIME-Version: 1.0
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How provoke call stack trace
References: <NRWh.pL.3@gated-at.bofh.it>
In-Reply-To: <NRWh.pL.3@gated-at.bofh.it>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@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/