[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] XaAES 1.55 + NetSurf



Ole, 27.03.2013 22:42:42:

NetSurf requires the Eddi cookie to be present (to read screen info), is there anything interesting about your system (anything could be interesting =))?

aranym+fVDI ;-)

You can get the screen-info also from v_opnwk and vq_extnd.

So all that looks clean to me, but yes, calling (reading) a function which doesn't belong to the process memory is maybe forbidden in some mmu setups,...

Maybe allocating the cookie in global memory or switching to supervisor could help, I don't know.

 Can you compare the eddi value with the value 111C5AC (cookies.cpx)? if

The value is correct.

 Hm... trying to compile XaAES 1.6.0 for coldfire now...

Have fun :) Does the error also happen there?

I would send you some source-files with debug-information for a start.

BTW: I have a script to locate the function where an exception occurs, similar to addr2line, but I would need a netsurf-binary with debug-symbols for that.

--
Helmut Karlowski