public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Siva_Prasad_Reddy@3com.com
To: sourcenav@sources.redhat.com
Subject: Cross reference...
Date: Thu, 29 Mar 2001 17:58:00 -0000	[thread overview]
Message-ID: <88256A1F.00070E07.00@hqoutbound.ops.3com.com> (raw)

Hi,

I am Siva Prasad, working for 3Com.

I am using Source Navigator and it is really a great tool for developers. I
would like to appreciate your effort for the open source environment with great
tools like Source Navigator.

I got a small question...
* I am using "Cross Reference" more often when ever I start trace analyzing the
code. It works one way only, I mean, I can look for references from a particular
routine to what are called from that routine. Is there a possibility of looking
for what called this current routine?. I am using "grep" for finding who is
calling the current routine. I would love if that is available as part of "Cross
Reference". Is there any reason why this kind of feature not implemented. I
would like to lend my support in develop this feature if you think, it is
possible.

Your help regarding this would be great and highly appreciated.

Looking forward for your reply.

Thanks,
Siva Prasad.




             reply	other threads:[~2001-03-29 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29 17:58 Siva_Prasad_Reddy [this message]
2001-03-30 12:13 ` Ian Roxborough

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=88256A1F.00070E07.00@hqoutbound.ops.3com.com \
    --to=siva_prasad_reddy@3com.com \
    --cc=sourcenav@sources.redhat.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).