From: "Berek" <berek@usa.net>
To: "Ben Elliston" <bje@air.net.au>, "Raj, Ashok" <ashok.raj@intel.com>
Cc: <sourcenav@sources.redhat.com>
Subject: RE: problem with source navigator when run on linux kernel sources...
Date: Fri, 13 Oct 2000 17:37:00 -0000 [thread overview]
Message-ID: <NDBBJEBJPMNFKBGLKCNFEELEELAA.berek@usa.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0010140844090.26149-100000@moshpit.cygnus.com>
I've had the same problem, only on NT 4.0. It's dbimp. Goes into a loop and
pegs the cpu. Cannot reproduce at will. Happens one out of eight or nine
times. Reparsing same project. 560,000 plus lines. Does not happen on
smaller projects or subprojects. Only when combining subprojects into a
larger 500,000+ lines of code. May not be memory-related because the
machine(s) (PCs) on which this is happening both have 512 meg real and 1 gig
virtual.
> -----Original Message-----
> From: sourcenav-owner@sources.redhat.com
> [ mailto:sourcenav-owner@sources.redhat.com]On Behalf Of Ben Elliston
> Sent: Friday, October 13, 2000 17:45
> To: Raj, Ashok
> Cc: 'sourcenav@sources.redhat.com'
> Subject: Re: problem with source navigator when run on linux kernel
> sources...
>
>
> Hi,
>
> I tried both the 4.5.1 and 4.5.2 against linux sources, after it
> starts creating the project, one of the sub processes cbrowser???
> seems to just spin for ever. the progress bar shows 6% and never
> moves. Have you tried the snavigator on the linux tree? on small
> projects it seems ok. i would really like to use it on the kernel
> sources..
>
> What version of the kernel source tree are you trying to parse?
> That should
> make it possible to reproduce.
>
> Ben
>
>
prev parent reply other threads:[~2000-10-13 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-13 8:37 Raj, Ashok
2000-10-13 14:44 ` Ben Elliston
2000-10-13 17:37 ` Berek [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=NDBBJEBJPMNFKBGLKCNFEELEELAA.berek@usa.net \
--to=berek@usa.net \
--cc=ashok.raj@intel.com \
--cc=bje@air.net.au \
--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).