From: William Gacquer <wgacquer@ubisoft.fr>
To: sourcenav@sources.redhat.com
Subject: Buggy Xref?
Date: Mon, 26 Mar 2001 07:12:00 -0000 [thread overview]
Message-ID: <5D2A198567EED311BD0F009027A25C876CF726@SRVMAIL-ANN> (raw)
Hello
I have a lot of source code to parse. The code is working pretty
well ( this is the Rayman Revolution Playstation 2 game). I asked source
navigator to parse the code using a #define list I provide. These #defines
are correct. These are the #define of the release version. When I ask for a
"Reparse Project", its crashes like this :
"
Error: child killed: segmentation violation during xref-generation
for: public/mth/mth_flt.h
Source-Navigator had a problem generating Cross-Reference
information.
Cross-Reference information is not complete.
"
Without the #define list, it runs well.
How can I get the log of the x-ref generation to eventualy get the line
where the problem is?
Are you aware of that kind of bug?
Regards,
William Gacquer
PS : You already know how to parse the code. Now, the next step would be to
offer the opportunity to hide/unhide the code between #ifdef/#endif
reply other threads:[~2001-03-26 7:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5D2A198567EED311BD0F009027A25C876CF726@SRVMAIL-ANN \
--to=wgacquer@ubisoft.fr \
--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).