From: Ben Elliston <bje@redhat.com>
To: Laurent Lopez <l.lopez@cstelecom.com>
Cc: <sourcenav@sources.redhat.com>
Subject: Re: snavigator 452 freeze while referenceing Linux kernel code
Date: Mon, 04 Dec 2000 16:22:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0012051120550.6575-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <14891.47853.857633.853088@verif03.fty.cstelecom.com>
In fact a single file make snavigator 4.5.2 freeze, this file is added
to this mail. Just put this file in a directory and try to create a
new projetc with this directory. Snavigator seems to enter in an
endless loop while the "Scanning Project ..." window is open.
The following technique may help -- I use it often.
$ echo arch.c > file.list
$ gdb /path/to/cbrowser -y file.list -p /bin/cat
(-y says where to find the file manifest, -p says which program will process
the parser's output--which is usually dbimp).
I would normally try to look into this myself, but I'm very busy right now.
Good luck!
prev parent reply other threads:[~2000-12-04 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 7:46 Laurent Lopez
2000-12-04 16:22 ` Ben Elliston [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=Pine.LNX.4.30.0012051120550.6575-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=l.lopez@cstelecom.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).