From: "Jim Avera" <jima@simplex.com>
To: <sourcenav@sources.redhat.com>
Subject: snavigator bug after 'unload directory'
Date: Mon, 18 Mar 2002 09:10:00 -0000 [thread overview]
Message-ID: <AGEHKAPBGMHCDOPJJJFAOEHBCAAA.jima@simplex.com> (raw)
In-Reply-To: <AGEHKAPBGMHCDOPJJJFACEGOCAAA.jima@simplex.com>
Hi,
This is a bug report on Source Navigator 5.0.0 under Cygwin.
It corrupted the project and stopped working after the following actions:
0. Loaded a large project with many subdirectories. About 3000 source files
altogether.
1. Tools->Reparse Project, then clicked the CANCEL button before it
finished (and confirmed the cancel in the subsequent dialog).
2. In the project editor, I used 'unload directory' to remove a directory
containing redundant copies of files
(it was a top-level include/ directory containing installed copies of
.h files which also existed in source directories elsewhere in the
project)
3. Tools->Reload Project (seemed to complete almost instantaneously)
4. Tools->Reparse Project
At this point sn seemed to read a few files (possibly from only a single
directory)
and stop, as though it were done. No xref was generated, or else it took
such a
short time that I didn't/couldn't observe it (xref is enabled in the
Project preferences).
Subsequent attempts to reparse the project (~3000 source files) had the
same
behavior - files flashed by in the progress box for 1-2 seconds, and then
nothing.
I suspect that deleting the directory made sn forget about most of the
remaining files,
though they are still displayed in the project file browser. Maybe only the
"unloaded"
directory is being scanned?
The project seems to be hopelessly corrupted. I had to abandon it and
create another.
prev parent reply other threads:[~2002-03-18 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 1:46 SN50 build issues on Solaris 8 Jim Avera
2002-03-18 9:10 ` Jim Avera [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=AGEHKAPBGMHCDOPJJJFAOEHBCAAA.jima@simplex.com \
--to=jima@simplex.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).