Now that the 0.8.7 release branch is made, I've added an implementation
of LocalConnection in trunk.
It should work on POSIX systems and build on Windows (but not work
there). I apologize in advance if there are compilation problems. It
should be easy to add the Windows implementation (see
Il 11/02/2010 14.30, Benjamin Wolsey ha scritto:
Now that the 0.8.7 release branch is made, I've added an implementation
of LocalConnection in trunk.
actually i have this error:
SharedMem.cpp:157: error: conversion from
‘gnash::SharedMem::attach()::semun’ to non-scalar type ‘semun’
SharedMem.cpp:157: error: conversion from
‘gnash::SharedMem::attach()::semun’ to non-scalar type ‘semun’
requested
SharedMem.cpp:166: error: conversion from
‘gnash::SharedMem::attach()::semun’ to non-scalar type ‘semun’
requested
If you drop the local definition of the union semun, does it
well, it is full of #ifdef already.. for the rest it seems to be
compiled without any problem. Do you have an swf test case to see if
all shm system is working correctly?
testsuite/misc-ming.all/LCTestRunner
You can also run LC-Test.swf and LC-Receive.swf simultaneously.
Online example:
(but as explained, it will probably only work once because of the way
the plugin exits).
This problem should be fixed too now with a signal handler (revno
11936). We might consider adding this to the release branch too, as it
is better to make sure things are cleaned up.
--
The current
On 02/11/10 12:59, Benjamin Wolsey wrote:
This problem should be fixed too now with a signal handler (revno
11936). We might consider adding this to the release branch too, as it
is better to make sure things are cleaned up.
Is this fixing an old bug, or one you only noticed with your
Is this fixing an old bug, or one you only noticed with your changes
for LocalConnection ?
The real problem is with LocalConnection, but note that all sorts of
things are done on exit, including flushing shared objects (if they
haven't already been flushed), and none of this will happen if
On 02/11/10 14:31, Benjamin Wolsey wrote:
So there's no doubt we should be doing this, but the flip side is that
it creates more opportunities to hang the browser, so maybe it needs
more than a couple of days' testing before going into a release.
I agree it's a good idea to handle this
8 matches
Mail list logo
