RE: EuGrid - was Runs w/Interpreter but not as .exe

new topic     » goto parent     » topic index » view thread      » older message » newer message

Derek,

Derek Parnell wrote:
> Jonas,
> 
> If lParam is a value and not a pointer, and Phil is using it as the 
> FIRST 
> parameter to fetch() then there could be problems.

Is lParam passed as a value in the onEvent handler?  I'm not sure.

> 
> How did you detect this anomoly, Jonas? Did using the safe-mode help you 
> or 
> not?
> 
> Did you actually find anything wrong with my safe-mode tk_mem.e? If so, 
> I'd 
> like to fix it.
> 

Actually there was nothing wrong your safe mode of tk_mem.e.  I have 
some other routines that were using Eu's allocate() and free() routines 
so I also needed to use safe.e and since safe.e is not compatible with 
tk_mem.e I just replaced the windows routines in tk_mem.e to 
allocate/free memory with Euphoria's routines.  The fetch() call in 
EuGrid was just the first thing I ran into and all the time I had to 
spend on it today (I also had to use register_block in several places to 
omit checking of valid memory allocated in a .dll).

I'm telling you, this has me really frustrated.  No matter how the 
source is arranged it runs fine interpreted but as soon as it is bound 
it starts bombing.  I think using safe memory handling is the only way 
to track this down.  I'm not even convinced the problem is in EuGrid but 
since I started having this problem when I began using the new version I 
figured it was a good place to start.

What I hope to have after this is solved is a good handle on how to 
track this down in the future, maybe even share how I went about finding 
the problem (IF I find it, that is).

Jonas

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu