hi,
within systems/x11/x11input.c there might be a bug on our side.
the later on pasted output of that sigsegv is caused within the
static void*
x11EventThread( DirectThread *thread, void *driver_data ...
function lin 295 ... of mentioned file.
if i do run my application, that is using dfb, with x11 as output window -
everything is fine.
if i do run the same application for debugging purposes with valgrind, i do get
the following output
(*) DirectFB/Config: Parsing config file '/etc/directfbrc'.
---------------------- DirectFB v0.9.23 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
-----------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2005-10-18 19:44)
(*) Direct/Memcpy: Forced to use MMX optimized memcpy()
(*) Direct/Thread: Running 'X11 Input' (INPUT, 449)...
(!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: X11 Input 0.1 (Martin Lutken)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence integrated
media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
dfb_x11_set_video_mode
dfb_x11_set_video_mode_handler
==32070== Thread 2:
==32070== Invalid read of size 4
==32070== at 0x1C3AEDEA: XCheckMaskEvent (in /usr/lib/libX11.so.6.2)
==32070== Address 0x4D0 is not stack'd, malloc'd or (recently) free'd
==32070==
==32070== Process terminating with default action of signal 11 (SIGSEGV)
==32070== Access not within mapped region at address 0x4D0
==32070== at 0x1C3AEDEA: XCheckMaskEvent (in /usr/lib/libX11.so.6.2)
==32070==
directfb is cvs of today.
xorg is 6.8.2
behaviour is reproduceable
i do not exactly know, if xorg or directfb is causing this behaviour.
but definately there's something wrong with one of them, or even both.
regards
marcel
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
