well... after a sleepless night (spent mostly watching tv, sadly), I can say this:
"looks" like callbacks, time to time, are executed twice... one with a bad arguments pointer and the subsequent correctly. I conclude this after creating a callback who returns "<<ERROR>>" as a list element (in a tableView:objectValueForTableColumn:row:), when the address is "invalid" (address >= 1000000000), and logging it... the callback is executed, and some times it answers "<<ERROR>>", but the list NEVER shows "<<ERROR>>".
is this right? no idea (yet) if this is right... how to fix it? even less idea (yet)
best, Esteban
El 02/03/2011, a las 6:15a.m., Igor Stasenko escribió:
On 1 March 2011 22:59, Esteban Lorenzano estebanlm@gmail.com wrote:
Still no clue here, but there some more data: If I check if the address is valid (< 10000000 in this case), and return a dummy value in that case, the program execution continues without problem (bad data, of course), so... is not a bad dealloc problem, maybe something when entering a callback?
btw... I'm using a 5.7.4... maybe I need to use a cog?
heh.. callbacks + Alien.. Don't expect any help there. We don't have too much people with enough expertise to be able to help with that.
I just hoping that at some day it will change. :)
thanks :) Esteban
-- Best regards, Igor Stasenko AKA sig.