From: Robert Schweikert <Robert.Schweikert@abaqus.com>
To: linux-kernel@vger.kernel.org
Cc: Robert Schweikert <rjschwei@abaqus.com>
Subject: process stack question
Date: 19 Jun 2003 15:18:42 -0400 [thread overview]
Message-ID: <1056050322.24403.116.camel@cheetah.hks.com> (raw)
I have been searching for some documentation on how to get at
information regarding the process stack but I didn't find much and from
what I found it was not clear to me how I could use the information.
Here is what I am after.
We have some rudimentary memory tracking tools in our application and
I'd like to put some debug output in that allows me to write the name of
the routine I am in to some debug log.
My thinking is that I should be able to get a hold of the process call
stack and using the top of the stack I should have the name of the
function/method I am in.
Any help on how to go about this would be appreciated. A pointer to any
documentation on how to get a hold of the stack, or the public API for
this is of course welcome.
Thanks,
Robert
--
Robert Schweikert <Robert.Schweikert@abaqus.com>
ABAQUS
next reply other threads:[~2003-06-19 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 19:18 Robert Schweikert [this message]
2003-06-19 19:35 ` Paul Rolland
2003-06-20 1:02 Perez-Gonzalez, Inaky
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=1056050322.24403.116.camel@cheetah.hks.com \
--to=robert.schweikert@abaqus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjschwei@abaqus.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
all inboxes | Powered by JetHome®