Sat 11 Aug 2007 01:17:21 PM UTC, comment #4:
>Thank you for your help. I tried using this file and
> RTIG just stops as soon as it gets to the offending
> line. My client spits out the following:
>
> ~/delta3d $ ./bin/testHLA terminate called after
> throwing an instance of 'RTI::RTIinternalError'
> Aborted
> ~/delta3d $ RTIA has thrown NetworkError exception.
> Reason: Connection closed by client.
Another error may be thrown on the RTIG console
you should look at it when lauching your federate.
>
> I tried, for simplicity, just deleting the offending
> lines completely and the whole FED file is parsed.
> The
> client then crashes with an RTI::NameNotFound.
Which is normal :))
The federation now lacks the interaction parameter
you've just deleted :=))
> I get the same results if I apply the patch that you provided.
Same result as what?
'RTI::RTIinternalError'
or
'RTI::NameNotFound'
or
the primary parse error.
If it is the parse error you should continue
to tweak the syntax.yy in order to get the parsing
right.
After that, you "MAY" get RTI::Internal Error
then the next step should be to run testHLA inside a debugger
in order to track the exception.
When you have the exception traceback put it here
on the tracker and I will try to help you to get it fixed.
> From the little I know of syntax descriptions, the YY
> file seems to include the proper case. Is there any
> way I could get more information about the error that
> it is throwing? I already compile with
> YYERROR_VERBOSE defined.
The parser won't give you more information than
something like
"unexpected CLASS, expecting R_PAR"
If you want me to be able to reproduce your bug
may be you can explain me how to reproduce it form the ground up.
0) how to install delta3d (configure option used etc...)
1) how to launch the test
Thank you for this CRETI bug hunting session.
|