Caught signal 8

Hi all,

when i try to run a dfb application on my arm target board i get the following error

~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.0 |~~~~~~~~~~~~~~~~~~~~~~~~~~
(c) 2001-2008 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2009-04-07 11:08) [ DEBUG ]
(*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER 0/0] <2093056>...
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(*) FBDev/Surface: Allocated 640x480 16 bit RGB32 buffer (index 0) at offset 0 and pitch 0.
(!) [ 1381: 0.000] --> Caught signal 8 (sent by pid 1381, uid 0) <--
(!!!) *** WARNING [still objects in 'Layer Region Pool'] *** [object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Context Pool'] *** [object.c:241 in fusion_object_pool_destroy()]
Floating point exception

would someone help me know why possibly i am getting this problem

Dear mathb,
you wrote:

when i try to run a dfb application on my arm target board i get the following error

I have the same problem, too.

(!) [ 2830: 0.000] --> Caught signal 8 (unknown origin) <--
(!!!) *** WARNING [still objects in 'Layer Region Pool'] *** [object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Context Pool'] *** [object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Surface Pool'] *** [object.c:241 in fusion_object_pool_destroy()]
Floating point exception


Do you have a idea where the floating point exception is comming from, now?

Thank you very much!
Bastian.

Online searching showed many people with this same issue and I had it this morning. I thought I would post my solution for anyone else encountering this.

Debugging led me to believe the issue was occuring due to 'pitch' being 0 when used for division in the call to dfb_fbdev_set_mode in fbdev.c primarySetRegion.

I resolved my Caught Signal 8 - Floating Point Exception issue by setting the line_length field of fb_fix_screeninfo to a non-zero value.

My display will be a fixed size so this is fine for me but others may need to update the value if it needs to change.

Pitch is the width of the buffer in bytes, see link:
http://www.x.org/wiki/Development/Do...VideoCardsWork

test reply