From: Arthur Davis <adavis@torrentnet.com>
Subject: buffer stack
Date: Tue, 24 Jun 2003 14:04:45 -0400 [thread overview]
Message-ID: <3EF892BD.5080708@torrentnet.com> (raw)
I spend a lot of time looking through code that spans many files and
tracing call stacks as one function calls another which calls another
.... I use cscope to help me navigate down through the code, but coming
back up the call stack is a problem. Is there a package that is able to
keep a stack of locations (buffer and point in buffer) to make this task
easier?
For instance: f1() in file A calls f2() in file B which calls f3() back
in file A. I'm looking for something that will allow me to pop back
from f3() in file A to f2() in file B and then back to f1() in file A.
Any suggestions?
Arthur
next reply other threads:[~2003-06-24 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 18:04 Arthur Davis [this message]
[not found] <mailman.8577.1056477908.21513.help-gnu-emacs@gnu.org>
2003-06-24 19:42 ` buffer stack Kai Großjohann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EF892BD.5080708@torrentnet.com \
--to=adavis@torrentnet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).