Denis Oliver Kropp wrote:
> 
> nitin sharma schrieb:
>> Hi All,
>> 
>> I am experiencing the following situation.
>> 
>> I have Gtk-DFB setup.
>> In this environment, I execute APP1.
>> Subsequently, I execute APP2 (APP1 is still in execution ).
>> Then APP1 exits (APP2 is still in execution ).
>> 
>> Tha application APP2 also stops working.
>> ____________________________________
>> (!!!)  *** WARNING [out of shared memory] *** [surfaces.c:1506 in
>> dfb_surface_allocate_buffer()]
>>  (#) DirectFBError [gdk_display_dfb_create_surface ]: Out of shared
>> memory!
>> 
>>  Gdk-DirectFB-ERROR **: file gdkpixmap-directfb.c: line 180
>> (gdk_pixmap_new): assertion failed: (surface != NULL)
>>  aborting...
>>  (!) [15809:   28.309] --> Caught signal 6 (unknown origin) <--
>>   (!!!)  *** WARNING [refusing shutdown in slave] *** [core.c:956 in
>> dfb_core_arena_shutdown()]
>>  (!) Direct/Thread: Killing 'Fusion Dispatch' (15810)!
>> ____________________________________
>> 
>> My guess is, this a known scenario.
>> 
>> Is there any plan to resolve such a scenario?
> 
> The first application started is the master process. It's running
> input drivers, dispatching events to other processes. It is the
> master cleaning up resources of crashed or even normally exiting
> applications.
> 
> The master really needs to run the whole time. You can use another
> application just sitting there to run the master operations, if
> you want to quit APP1 before APP2.
> 

I also had these problem.APP1,APP2,APP3...use surface->lock to share the
screen which are running well togather without keyboard input just using 
/dev/mice directly.If I use DFB input event buffer on APP1(first run),only 
APP1 can show,other apps can run but like wait at surface->lock and without
display.:confused:

this is APP1 running like a server:
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 13097)...
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) DirectFB/Genefx: MMX detected and enabled
(!) Direct/Modules: Could not open module directory
`/usr/local/lib/directfb-1.0
-0/gfxdrivers'!
    --> No such file or directory
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: SaWMan 0.1 (directfb.org)
(!) DirectFB/FBDev: Panning display failed!
    --> Invalid argument
(!) DirectFB/FBDev: Panning display failed!
    --> Invalid argument
(!) FUSION_CALL_RETURN    --> Input/output error
(!) FUSION_CALL_RETURN    --> Input/output error
dev id <1> name:IMPS/2 Mouse
dev id <0> name:Keyboard
VideoInit server
video format RGB16
req:width=640 height=480 bpp=16 default:w=640 h=480 bpp=16
test server 11 ? 11 and client 10 ? 0
Get event_buffer address:134568632
mouse postion (0,0)

this is APP2 running like a client:
(*) Direct/Thread: Running 'Fusion Dispatch' (MESSAGING, 13101)...
(*) DirectFB/Genefx: MMX detected and enabled
(!) Direct/Modules: Could not open module directory
`/usr/local/lib/directfb-1.0
-0/gfxdrivers'!
    --> No such file or directory
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org)
(!) DirectFB/FBDev: Panning display failed!
    --> Unknown error 4294967295
(!) FUSION_CALL_RETURN    --> Input/output error
(!) FUSION_CALL_RETURN    --> Input/output error
VideoInit client
video format RGB16
req:width=640 height=480 bpp=16 default:w=640 h=480 bpp=16
test server 11 ? 0 and client 10 ? 10


-- 
View this message in context: 
http://www.nabble.com/Multi-core-setup-architectural-issue----need-clarification-tf3080917.html#a12872226
Sent from the DirectFB Dev mailing list archive at Nabble.com.


_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to