Arnaud Derasse wrote: > Hi, > I need the debug support on DFB 1.1.1 but when I use --enable-debug, I > have this output : > > =======================| DirectFB 1.1.1 |======================= > (c) 2001-2007 The DirectFB Organization (directfb.org) > (c) 2000-2004 Convergence (integrated media) GmbH > ------------------------------------------------------------ > > (*) DirectFB/Core: Single Application Core. (2008-01-16 21:06) [ DEBUG ][ > TRACE ] > (*) Direct/Thread: Running 'H3600 TS Input' (INPUT, 71)... > (*) DirectFB/Input: H3600 Touchscreen 0.2 (directfb.org) > (!) Direct/Modules: Could not open module directory > `/usr/lib/directfb-1.1-0/gfxdrivers'! > --> No such file or directory > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) > (*) DirectFB/Core/WM: Default 0.3 (directfb.org) > (*) FBDev/Mode: Testing 800x480 RGB16 > (*) FBDev/Mode: Preparing switch to 800x480 RGB16 > (*) FBDev/Mode: Testing 800x480 RGB16 > (*) FBDev/Mode: Preparing switch to 800x480 RGB16 > > (*) FBDev/Mode: Testing 800x480 RGB16 > (*) FBDev/Mode: Preparing switch to 800x480 RGB16 > (*) FBDev/Mode: Testing 800x480 RGB16 > (*) FBDev/Mode: Preparing switch to 800x480 RGB16 > (*) FBDev/Mode: Testing 800x480 RGB16 > (*) FBDev/Mode: Preparing switch to 800x480 RGB16 > (!!!) *** UNIMPLEMENTED [fusion_skirmish_lock_count] *** [lock.c:593] > (!) [Main Thread 0.000] ( 69) *** Assertion > [fusion_skirmish_lock_count( &surface->lock, &lock_count ) == DFB_OK] failed > *** [surface_buffer.c:183 in dfb_surface_buffer_lock()]
Please try the option "fatal-level = none". The assertion is wrong, because in the single app core the lock count check is not implemented. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
