Hi Nicolas, If you are using linux as OS, you do the following steps:
- in shell type: ulimit -c 8000 - run your application, with the signal 11 you'll get a (core dumped) - check you current directory and you'll find a file named "core" or "core.<PID>" - run gdb <the_name_of_you_application> <the core file> - gdb will analyse the core and gives you which line of code generated the signal - to have a full stack, just type "bt" you should compile your application indebug mode to have useful data. for example: $> gdb df_dok core.2345 . . . gdb>bt hope this will help you. regards. On Fri, Nov 21, 2008 at 1:20 AM, Masse Nicolas <[EMAIL PROTECTED]>wrote: > Hi, > > these days, i had a big problem when trying to use directfb. It just > doesn't work, because the initialisation is failling. Here is what I > have: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.3.0 |~~~~~~~~~~~~~~~~~~~~~~~~~~ > (c) 2001-2008 The world wide DirectFB Open Source Community > (c) 2000-2004 Convergence (integrated media) GmbH > ---------------------------------------------------------------- > > (*) DirectFB/Core: Multi Application Core. (2008-11-19 23:52) > (*) Fusion/SHM: Using MADV_REMOVE (2.6.27.0 >= 2.6.19.2) > (*) Direct/Thread: Started 'Fusion Dispatch' (-1) [MESSAGING OTHER/OTHER > 0/0] <8388608>... > (*) Direct/Thread: Started 'VT Switcher' (20795) [CRITICAL OTHER/OTHER 0/0] > <8388608>... > (*) Direct/Thread: Started 'PS/2 Input' (20796) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20797) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: Macintosh mouse button emulatio (1) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20798) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: AT Translated Set 2 keyboard (2) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20799) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: Power Button (FF) (3) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20800) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: Power Button (CM) (4) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20801) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: PC Speaker (5) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Linux Input' (20802) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: ImExPS/2 Generic Explorer Mouse (6) 0.1 (directfb.org) > (*) Direct/Thread: Started 'Keyboard Input' (20803) [INPUT OTHER/OTHER 0/0] > <8388608>... > (*) DirectFB/Input: Keyboard 0.9 (directfb.org) > (!) [20789: 0.154] --> Caught signal 11 (at 0xb7eea0a0, invalid address) > <-- > (!) DirectFB/core/vt: Unable to disallocate VT! > --> Device or resource busy > > If you want more info, i've also tested after recompiling dfb with the > --debug flags, and > I had this (I've copied only the interresting part of the logs, because it > is very long): > ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.3.0 |~~~~~~~~~~~~~~~~~~~~~~~~~~ > (c) 2001-2008 The world wide DirectFB Open Source Community > (c) 2000-2004 Convergence (integrated media) GmbH > ---------------------------------------------------------------- > ... > (*) DirectFB/Input: Keyboard 0.9 (directfb.org) > (-) [Main Thread 0.193] (22981) Core/Input: > allocate_device_keymap( 0x94aa698, 0x94a8958 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMPool: > fusion_shm_pool_allocate( 0x20000184, 3584, clear, 0xbf9cb728 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: __shmalloc_brk( > 0x20120000, 0 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: _fusion_shmalloc( > 0x20120000, 3584 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: morecore( > 0x20120000, 4096 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: align( > 0x20120000, 4096 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: __shmalloc_brk( > 0x20120000, 4096 ) > (-) [Main Thread 0.193] (22981) Core/Input: init_axes( > 0x94a8958 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMPool: > fusion_shm_pool_allocate( 0x20000184, 12, clear, 0xbf9cb718 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: __shmalloc_brk( > 0x20120000, 0 ) > (-) [Main Thread 0.193] (22981) Fusion/SHMHeap: _fusion_shmalloc( > 0x20120000, 12 ) > (-) [Main Thread 0.193] (22981) Core/Input: input_add_device( > 0x94a8958 ) > (-) [Main Thread 0.193] (22981) Direct/Mem: + 148 bytes > [input.c:1163 in init_devices()] > (-) [Main Thread 0.193] (22981) Core/Input: -> probing > 'Joystick Driver'... > (-) [Main Thread 0.193] (22981) Direct/Mem: - number of > bytes of driver [input.c:1178 in init_devices()] -> 0x94a8530 > (-) [Main Thread 0.193] (22981) Direct/Mem: + 148 bytes > [input.c:1163 in init_devices()] > (!) [22981: 0.193] --> Caught signal 11 (at 0xb7fae060, invalid address) > <-- > (-) [Main Thread 0.193] (22981) DirectFB/Core: > dfb_core_destroy... > (-) [Main Thread 0.193] (22981) Direct/Signals: Removing handler > 0xb7f28320 for signal -1 with context 0x94aa698... > (-) [Main Thread 0.193] (22981) Direct/Mem: - number of > bytes of handler [signals.c:176 in direct_signal_handler_remove()] -> > 0x94aa020 > (-) [Main Thread 0.193] (22981) Fusion/Arena: > fusion_arena_exit( 'DirectFB/Core' ) > (-) [Main Thread 0.194] (22981) DirectFB/Core: Shutting down... > ... > if you want, I can give you the full log. > > > Note that I had the same problem with version 1.2.6, but I know the 1.0 > version was working well. > FYI, i'm using the kernel2.6.27 and compile dfb with these flags: > ./configure --prefix=/usr --sysconfdir=/etc --enable-static --enable-multi > \ > --enable-debug --enable-fbdev --enable-x11 --disable-sdl --disable-osx \ > --enable-unique --enable-zlib --enable-video4linux2 --with-tests > > > Thanks in advance, > bountykiller. > > > > _______________________________________________ > directfb-dev mailing list > directfb-dev@directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev >
_______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
