I've compiled DirectFB to mips on a Broadcom box. I'm encountering a weird situation where I'm getting a SIGTRAP in wm.c.
(-) [Main Thread 30.487] (19949) Core/WM: dfb_wm_init_stack( 0x44e888 ) (!) [Main Thread 30.487] (19949) *** Assertion [fusion_skirmish_lock_count( &stack->context->lock, &lock_count ) == DR_OK] failed *** [wm.c:540 in dfb_wm_init_stack()] (-) [Main Thread 30.487] (19949) - - : Direct/Assertion: Raising SIGTRAP... When I run the directfb tests (dfbtest_window), I can terminate normally and get past this statement. In GTK programs, I crash here. I'm noticing differences in objects such as core->shared when I go through dfb_core_create between GTK programs and the DFB test programs, but I don't understand how they are initialized differently. Anyone encountered this or have any ideas? -- View this message in context: http://www.nabble.com/DirectFB-1.3%2C-SIGTRAP-in-wm.c-tp21942587p21942587.html Sent from the DirectFB Dev mailing list archive at Nabble.com. _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
