[Gambas-bugtracker] Bug #2540: Gambas does not seem to be writing to same shared memory as local processes

[bugtracker at gambaswiki.org]

http://gambaswiki.org/bugtracker/edit?object=BUG.2540&from=L21haW4-

Comment #1 by Brian G:

How are you forking the other process, can you provide a project?

I am using this every day, and have no problems with a local shared segment
and tasks seeing the changes.

Do you create a task class? in the gambas application?

If you create the shared segment in the main of the app that spawns the other tasks
you don't have to map the memory in the forked class, it is already mapped when you fork.

So the main line creates the shared segment and mmaps it to the application,

now you start any number of tasks the memory is already mmaped into that forked task
you just access it from the forked, task.

Sample script outline attached.

If you try to remap it in the task it creates a new memory segment.

----------------------------------------------------------------------------

Attachment: TestTaskmmap.gbs