From: Martin Dalecki <dalecki@evision-ventures.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Brian Gerst <bgerst@didntduck.org>,
Simon Turvey <turveysp@ntlworld.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Generating a function call trace
Date: Fri, 30 Nov 2001 19:37:23 +0100 [thread overview]
Message-ID: <3C07D1E3.15F77C98@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111301035490.1600-100000@blue1.dev.mcafeelabs.com>
Davide Libenzi wrote:
>
> On Fri, 30 Nov 2001, 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).
>
> I thought it was a general question not a kernel code one.
> Sure -fomit-frame-pointer is on inside the kernel.
With the , well exception, of the scheduler, which does the task
switching by
overwriting his own return address on the stack by the address of the
next jump point in a process, and needs the frame
pointer therefore ;-).
next prev parent reply other threads:[~2001-11-30 18:48 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 [this message]
2001-12-01 19:00 ` Matt D. Robinson
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=3C07D1E3.15F77C98@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=bgerst@didntduck.org \
--cc=dalecki@evision.ag \
--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 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.