GameMonkey Script

Hi,
First i want to say thanks to gm developpers for this huge work, i'm using it for weeks and it's really perfect.

I think i may have found a little bug with the endon feature, (I'm using gm 1.29.0):

The main idea is when a endon block is reached, it creates a new "fake" block to kill the thread on a specific signal.
But I think that if this thread reaches after the endon, a real block (block, not endon), then it cancels the previous endon(s).

I wasn't able to recreate this with a small script (maybe because endon doesn't always return GM_SYS_BLOCK), but with my main script, i got this bug.
So i checked the gmMachineLib.cpp file, and i saw that a "block" return GM_SYS_BLOCK
such a return causes a machine->Sys_SwitchState(this,BLOCKED) (in gmThread.cpp/gmThread::PushStackFrame) -> http://prntscr.com/37t3qz
then in Sys_SwitchState, for the case BLOCKED, it does Sys_RemoveBlocks(a_thread) -> http://prntscr.com/37t4db

Therefore a block will remove a previous endon.

A fix, would be to not remove endon "blocks" in Sys_RemoveBlocks.

Am I right here ?

Thanks

Edit:
- Also I had a little question about "Sys_Signal", can I use GM_INVALID_THREAD for dest_thread and src_thread (as I want to send a signal from C++ code directly)
In the doc, it says that we can use GM_INVALID_THREAD for the dest_thread (this way all threads are signalled, but it says nothing about src_thread)
- In that case, if I create a signal from C++ code (not from a binding), can the object in the signal be collected by the GC ? because it's not really handled by the script, or is any object in a signal and a block not collected until the signal/block is "Sys_remove"?

Hi Korrion, welcome to the forum. Glad you're getting some use from GM.

You are most likely correct with the endon behavior and solution. I have to plead stupidity at the moment as I haven't looked through the code for a long time and can't give you an intelligent answer on the spot. It would be most helpful to make a small repro case so we can verify the issue and fix. I'll try to have a proper look at the code later this week and see if I can help. Briefly looking at the code and your description, the behavior does look as you describe.

In the meantime, feel free to experiment with a fix and play with / trace the VM implementation.

About your GC question... Any gmObject owned by C++ (not connected to other machine roots) must be added to the 'cpp owned' list otherwise it will be collected. For safety sake, newly created objects that are not yet connected, should have GC disabled around their initialization and connection. Looking at the gmSignal, a gmObject, which may be referenced there as gmVariable, IS a GC root once set on the thread. It should be safe.

Hi,

I originally added the "endon" extension, it's been a while since I looked over it so will take a look to see if I can repro the issue you're seeing. I'll see what I can do