Op 16-06-17 om 22:58 schreef Wolf via Lazarus:
now I understand the real bug is in my assumptions on what goes on
behind the screens. But that leads to another question: is there any
documentation where I can read up on this so that I may improve on my
programming, and particular debugging, ski
On Sat, Jun 17, 2017 at 11:25 PM, el es via Lazarus
wrote:
> But when, during the course of Queue()d callback,
> I FreeAndNil() the object that had the pointer to the callback procedure, I
> get SIGSEGV pointing at CheckSynchronize in Application. (address F0F0F0F0).
I don't know the details of t
On 18-Jun-17 11:20, Juha Manninen via Lazarus wrote:
On Sat, Jun 17, 2017 at 11:25 PM, el es via Lazarus
wrote:
But when, during the course of Queue()d callback,
I FreeAndNil() the object that had the pointer to the callback procedure, I
get SIGSEGV pointing at CheckSynchronize in Application.
El 18/06/2017 a las 22:44, el es via Lazarus escribió:
Hence the object, would have to have ITS callback routine be something
like a TNotifyEvent ( procedure(AObject: TSomeObject) of object, or
something), and the flag set is set when the callback returns to the
object context like
procedure
