Re: [gobo-eiffel-develop] Unhandled exception from gec-compiled tests

[Eric B. <er...@go...>]

Colin Adams wrote:
> It doesn't fix the problems where I get:
> 
> In test-case errorcode1030: Finishing early, having processed test case
> 'eeocode' in 'eif_except.h' not implemented
> 'stack_trace_string' in 'eif_except.h' not implemented
> Call on Void target!
> Unhandled exception
> 
> How much effort is involved to implement that?

The thing is that if `eeocode' and `stack_trace_string' are called,
it's because an exception has been raised in the first place. So
it might be interesting to know why an exception has been raise,
and when. So I suggest again that you put breakpoints in the generated
C code at the beginning of 'GE_raise', and also on function 'eeocode'.

It might be that eposix is relying too much on exceptions to program
expectable error cases! ;-)

The effort to implement it is not worth it. We are in the process to
move to exceptions implemented as objects.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com