From: dave.banham@tde.alstom.com
To: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: xref and referred by?
Date: Wed, 18 Oct 2000 01:11:00 -0000 [thread overview]
Message-ID: <C125697C.002CE281.00@mz02world.hq.dtr.gecalsthom.fr> (raw)
I too have also experienced this frustrating problem and I don't believe it is
anything to do with the fact that the xref database is still being
(re-)constructed - at least there is no progress bar indication.
I quite often end up using the grep tool to find the references - which it does
- but in doing so I am left questioning the accuracy of the xref tool. If xref
reports no referenced by information then I will try grep, but if it reports
some referenced by information am I seeing the complete picture or just part of
it?
Regards
Dave Banham
Bruce Stephens <bruce.stephens@messagingdirect.com> on 17/10/2000 16:45:41
To: sourcenav <sourcenav@sources.redhat.com>
cc: (bcc: Dave BANHAM/PCS/PCG/TDE/GECALSTHOM)
Subject: Re: xref and referred by?
Lonnie L VanZandt <tsys@uswest.net> writes:
> Why is it that many times the Referenced By information is
> unavailable? More often than not, I want to see who calls a function
> and not what that function calls. However, I can't seem to get SN to
> display the Referenced By information.
xref requires that certain databases be completely constructed. The
first time you run source navigator on a project, these can take some
time to construct (potentially hours, for large projects and/or slow
machines). There's a progress bar in the bottom right corner of any
SN windows while this is going on.
After the first time, SN should be faster to start up.
--
Bruce Stephens Bruce.Stephens@MessagingDirect.com
MessagingDirect(UK) Ltd <URL: http://www.MessagingDirect.com/ >
next reply other threads:[~2000-10-18 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 1:11 dave.banham [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 4:57 dave.banham
2000-11-14 8:55 Mark Thornber
2000-10-19 3:01 dave.banham
2000-10-19 7:58 ` Berek
2000-10-19 22:08 ` Mo DeJong
2000-10-17 8:36 Lonnie L VanZandt
2000-10-17 8:45 ` Bruce Stephens
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=C125697C.002CE281.00@mz02world.hq.dtr.gecalsthom.fr \
--to=dave.banham@tde.alstom.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).