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

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> 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:

    Eric> Do you get the same problems under Windows?

I've never tried to run the test suite under Windows, as it uses some
extra tools such as xmllint.

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

I will try that.

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

How do I set a break point?
-- 
Colin Adams
Preston Lancashire