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

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

Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault <er...@go...> writes:
> 
>     Eric> I have no idea how to debug what is going on in the Boehm
>     Eric> GC.  Since you are using Linux, you can perhaps try valgrind
>     Eric> (first with no GC and then with GC) to see if there is any
>     Eric> memory corruption in the C code generated by gec (or less
>     Eric> likely, in the Boehm GC).
> 
> There don't appear to be any problems without the garbage collector
> (of course, there are a lot of memory leaks).

> There are problems detected with the gc enabled. Here is the valgrind
> output:

Do you get the same problems under Windows?

Can you try to compile the Boehm GC with the option -DLARGE_CONFIG?

One other thing that I would be interested in, even if it does not
crash at the same location each time, is to know at which stage
in the execution trace the message "Unhandled exception" is printed.
Could you try to put a break point in the C code at the beginning of
the C function 'GE_raise' and see what the execution trace looks like?

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