From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How provoke call stack trace
Date: Mon, 03 Nov 2003 20:32:14 +0100 [thread overview]
Message-ID: <3FA6AD3E.5090706@softhome.net> (raw)
In-Reply-To: <NRWh.pL.3@gated-at.bofh.it>
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 |*|*|*|
next parent reply other threads:[~2003-11-03 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NRWh.pL.3@gated-at.bofh.it>
2003-11-03 19:32 ` Ihar 'Philips' Filipau [this message]
2003-11-03 18:38 How provoke call stack trace Ihar 'Philips' Filipau
2003-11-03 18:45 ` Michael Buesch
2003-11-03 18:51 ` Roland Dreier
2003-11-03 18:53 ` Muli Ben-Yehuda
2003-11-03 20:24 ` Ihar 'Philips' Filipau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FA6AD3E.5090706@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox