All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How provoke call stack trace
Date: Mon, 03 Nov 2003 21:24:28 +0100	[thread overview]
Message-ID: <3FA6B97C.6070707@softhome.net> (raw)
In-Reply-To: <20031103185334.GS32115@actcom.co.il>

Muli Ben-Yehuda wrote:
> On Mon, Nov 03, 2003 at 07:38:39PM +0100, Ihar 'Philips' Filipau wrote:
> 
> 
>>   Is there any function which can be used by module to just 
>>investigate some given call path?
> 
> 
> Assuming 2.6, call dump_stack(). If you want greater flexibility,
> investigate show_trace() and friends. 
> 
> Hope this helps, 

   I'm sitting right now on 2.4.22 - so no 2.6 nicities.
   I actually wanted to have something like this on ppc - but ppc has no 
dump_stack() implemented.

   Thanks any way.

   [ Just checked 2.6 - ppc has dump_stack() now. Nice. It looks like 
all archs have implemented it in 2.6. Cool. ]

-- 
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           |*|*|*|


  reply	other threads:[~2003-11-03 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [not found] <NRWh.pL.3@gated-at.bofh.it>
2003-11-03 19:32 ` 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=3FA6B97C.6070707@softhome.net \
    --to=filia@softhome.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.