Hello all In my application I have incorporated application close capability by mouse and keyboard like in df_video.c But sometimes the system hangs on terminating the application. My log file (last lines of the log) in such system hang-up case comes as follows:-- The only thing which I can understand is that the thread corresponding to keyboard or mouse is not terminated properly as evident from log below in the end lines. Please suggest measures to eliminate this bug.
(-) [Main Thread 47.410] ( 3091) Core/Layers: dfb_layer_region_flip_update( 0x80c5b88, 0xbfffd9d0, 0x00000000 ) <- [160, 70 - 320x240] (-) [Main Thread 47.410] ( 3091) Core/Layers: -> Going to copy portion... (-) [Main Thread 47.410] ( 3091) Core/Layers: -> Waiting for pending writes... (-) [Main Thread 47.410] ( 3091) Core/Layers: -> Copying content from back to front buffer... (-) [Main Thread 47.411] ( 3091) Core/Layers: -> done. (-) [Main Thread 47.411] ( 3091) IDirectFBWindow: IDirectFBWindow_React() (-) [Main Thread 47.411] ( 3091) IDirectFBWindow: IDirectFBWindow_React() (-) [Main Thread 47.412] ( 3091) Fusion/Object: -> destructor done. (-) [Main Thread 47.412] ( 3091) Fusion/Object: == Surface Pool == (-) [Main Thread 47.413] ( 3091) Fusion/Object: -> dead object 0x80cb760 [24] (-) [Main Thread 47.413] ( 3091) Fusion/Object: -> calling destructor... (-) [Main Thread 47.413] ( 3091) Core/Surface: destroying 0x80cb760 (320x240) (-) [Main Thread 47.414] ( 3091) Fusion/Object: -> destructor done. (-) [Main Thread 47.414] ( 3091) IDirectFBWindow: -> releasing cursor shape... (-) [Main Thread 47.414] ( 3091) IDirectFBWindow: -> done. (-) [Main Thread 47.429] ( 3091) Fusion/Object: == Surface Pool == (-) [Main Thread 47.430] ( 3091) Fusion/Object: -> dead object 0x80cb2c8 [23] (-) [Main Thread 47.430] ( 3091) Fusion/Object: -> calling destructor... (-) [Main Thread 47.430] ( 3091) Core/Surface: destroying 0x80cb2c8 (320x240) (-) [Main Thread 47.431] ( 3091) Fusion/Object: -> destructor done. (!) [ 3091: 47.432] --> Caught signal 11 (at 0xc, invalid address) <-- (-) [Main Thread 47.432] ( 3091) DirectFB/Core: dfb_core_destroy... (-) [Main Thread 47.432] ( 3091) Direct/Signals: Removing handler 0x40068fe4 for signal -1 with context 0x8056750... (-) [Main Thread 47.432] ( 3091) DirectFB/Core: Shutting down... (-) [Main Thread 47.432] ( 3091) DirectFB/CoreParts: Going to shutdown 'wm' core... (-) [Main Thread 47.433] ( 3091) DirectFB/CoreParts: Going to shutdown 'layers' core... (-) [Main Thread 47.433] ( 3091) Core/Layers: Removing region (0, 0 - 800x600) from 'FBDev Primary Layer'. (-) [Main Thread 47.435] ( 3091) DirectFB/CoreParts: Going to shutdown 'screens' core... (-) [Main Thread 47.436] ( 3091) DirectFB/CoreParts: Going to shutdown 'gfxcard' core... (-) [Main Thread 47.438] ( 3091) DirectFB/CoreParts: Going to shutdown 'input' core... (-) [Main Thread 47.438] ( 3091) Direct/Thread: Canceling 3093. (-) [Main Thread 47.442] ( 3091) Direct/Thread: Canceling 3094. (!) [Keyboard Input 47.445] ( 3096) *** Assertion [wm_local != NULL] failed *** [wm.c:454 in dfb_wm_process_input()] (-) [Keyboard Input 47.446] ( 3096) Direct/Assertion: Sending SIGTRAP to process group 3091... (-) [Keyboard Input 47.446] ( 3096) Direct/Assertion: ...didn't catch signal on my own, calling _exit(-1). _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
