public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Siva_Prasad_Reddy@3com.com
Cc: sourcenav@sources.redhat.com
Subject: Re: Cross reference...
Date: Fri, 30 Mar 2001 12:13:00 -0000	[thread overview]
Message-ID: <3AC4E8CD.C885347E@redhat.com> (raw)
In-Reply-To: <88256A1F.00070E07.00@hqoutbound.ops.3com.com>

Siva_Prasad_Reddy@3com.com wrote:
> 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.

so basically, you've found how to see which functions are called from 
function X and you'd now like to see which functions are calling
function X.

On the Xref window they are to buttons with pointing hands on
them. The button pointing to the right will should you the
calls made by the current function, the button pointing to the
left shows you the calls made to that function.

There maybe X-ref issues with certain languages which would
stop this working, but I'm currently unfamiliar with them.

Another useful point is the "Details to" and Details by"
options which can be accessed by right clicking over a X-ref
symbol.  This is most useful when driving a editor pane (i.e.
add and editor view to the Xref tab).

Ian.

      reply	other threads:[~2001-03-30 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29 17:58 Siva_Prasad_Reddy
2001-03-30 12:13 ` Ian Roxborough [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=3AC4E8CD.C885347E@redhat.com \
    --to=irox@redhat.com \
    --cc=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).