From: girke@itu304.ut.TU-Berlin.DE
To: sourcenav@sources.redhat.com
Subject: Problem under WinNT4 Server SP5
Date: Thu, 30 Nov 2000 07:19:00 -0000 [thread overview]
Message-ID: <Pine.A32.3.96.1001128102630.8134A-100000@itu304.ut.TU-Berlin.DE> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Hi,
I have a problem with the xref part of SN. After parsing my project I got
the following messages:
1.
Dr.Watson: dbimp.exe Access violation (0xc0000005), adress 0x0043b267
2.
Error: child process exited abnormally -> SN had a problem generating
Cross-Reference information. CR information is not complete.
3.
dbopen error: D:/Develop/db_transfer/.snprj/db_trans.by:Invalid argument
My project is a MS VJ++ 6.0 with 28 source files and about 10.000 lines of
code.
Do you have any idea?
Thanks in advance
Mario Girke
Institut für Technischen Umweltschutz
Technische Universität Berlin
-------------------------------------------
girke@itu304.ut.tu-berlin.de, girke@gmx.net
next reply other threads:[~2000-11-30 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 7:19 girke [this message]
2000-11-30 15:57 ` Ben Elliston
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.A32.3.96.1001128102630.8134A-100000@itu304.ut.TU-Berlin.DE \
--to=girke@itu304.ut.tu-berlin.de \
--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).