[omniORB] o2be_internal_error
Sai-Lai Lo
S.Lo@orl.co.uk
Tue, 14 Apr 1998 14:34:32 +0100
>>>>> Gary D Duzan writes:
> It took me while to figure out that omniidl2 was core dumping
> because I had "long long" in some IDL, which is not supported, and the
> parser was throwing an o2be_internal_error exception. There should
> probably be someone catching this exception, printing the appropriate
> message, and exiting. I found some code in o2be_cfe_interface.cc to do
> something like this, but it is inside an "#if 0" block and so never
> gets called. Can this be safely reenabled? It seems a shame to core
> dump on an exception when it can at least print a decent error
> message.
Gary,
The '#if 0' block can be enabled to catch the exception. I left it out for
ease of debugging because that will cause it to core dump and one can
locate where the exception was thrown by 'dbx omniidl2 core'. I'll fix the
code to stop it throwing internal error at some stage.
Sai-Lai