public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matt D. Robinson" <yakker@alacritech.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
	Simon Turvey <turveysp@ntlworld.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Generating a function call trace
Date: Sat, 01 Dec 2001 11:00:37 -0800	[thread overview]
Message-ID: <3C0928D5.7E876339@alacritech.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111300900050.1600-100000@blue1.dev.mcafeelabs.com> <3C07CDF9.F1069C71@didntduck.org>

Try using 'lcrash', part of the LKCD project:

	http://lkcd.sourceforge.net/

I'm not sure what you mean by arbitrarily (meaning, it could be
at a snapshot point in time, or it could be while it is running,
etc.)  E-mail me if you have further questions, I'll try to help.

--Matt

Brian Gerst wrote:
> 
> Davide Libenzi wrote:
> >
> > On Fri, 30 Nov 2001, Simon Turvey wrote:
> >
> > > Is it possible to arbitrarily generate (in a module say) a function call
> > > trace?
> >
> > gcc has builtin macros to trace back or ( on x86 ) you can simply chain
> > through %esp/%ebp
> 
> That only works if you compile with frame pointers, which the kernel
> turns off for performance reasons (due to register pressure on the x86).
> 
> --
> 
>                                 Brian Gerst

      parent reply	other threads:[~2001-12-01 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 15:13 Generating a function call trace Simon Turvey
2001-11-30 15:33 ` Martin Dalecki
2001-11-30 16:19   ` Petr Vandrovec
2001-11-30 17:02 ` Davide Libenzi
2001-11-30 18:20   ` Brian Gerst
2001-11-30 18:39     ` Davide Libenzi
2001-11-30 18:37       ` Martin Dalecki
2001-12-01 19:00     ` Matt D. Robinson [this message]

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=3C0928D5.7E876339@alacritech.com \
    --to=yakker@alacritech.com \
    --cc=bgerst@didntduck.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=turveysp@ntlworld.com \
    /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