Quoting Sven Neumann:
> Hi,
>
> Selwyn Tang <[EMAIL PROTECTED]> writes:
>
> > Maybe a dumb question: what is the meaning of "trace support" in
> > configurating directfb? What good can it do and how should I use it?
>
> It can be helpful when you need to debug DirectFB applications. In
> case of a crash you will get a back trace similar to what gdb offers
> but limited to DirectFB functions. Of course there's a considerable
> overhead involved when this feature is enabled, so you should only use
> it for development.
>
> Dok, please correct me if this isn't correct, since I never used this
> feature myself.
There's nothing wrong, but here are some more details ;)
All cases of stack trace dumping:
- error messages
- failing assumptions/assertions
- signal handler
The overhead got quite small a few days ago. I switched from gettid() to
thread specific storage.
Here's a sample output:
(*) parsing config file '/etc/directfbrc'.
(*) parsing config file '/home/dok/.directfbrc'.
---------------------- DirectFB v0.9.21 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2003 convergence GmbH
-----------------------------------------------------------
(*) Multi Application Core. (with MMX support) (2004-01-15 12:08)
(*) DirectFB/misc/memcpy: forced to use MMXEXT optimized memcpy()
(*) DirectFB/InputDevice: Virtual Input 0.3 (Convergence GmbH)
(*) DirectFB/InputDevice: PS/2 Mouse 0.9 (convergence integrated media GmbH)
(*) DirectFB/InputDevice: Keyboard 0.9 (convergence integrated media GmbH)
(*) MMX detected and enabled
(!) DirectFB/core/modules: ABI version of 'libdirectfb_sis315.so' (20) does not match
21!
(-) DirectFB stack trace of 28359
'-> DirectFBCreate()
'-> dfb_core_create()
'-> fusion_arena_enter()
'-> dfb_core_arena_initialize()
'-> dfb_core_initialize()
'-> dfb_core_part_initialize()
'-> dfb_gfxcard_initialize()
'-> dfb_modules_explore_directory()
'-> open_module()
'-> dfb_modules_register()
(*) DirectFB/GraphicsDevice: Matrox G400/G450/G550 0.6 (convergence integrated media
GmbH)
(!) [28359: 0.584] *** Assertion [funcs->InitEncoder != NULL] failed! ***
screens.c:130 in dfb_screens_initialize()
(-) DirectFB stack trace of 28359
'-> DirectFBCreate()
'-> dfb_core_create()
'-> fusion_arena_enter()
'-> dfb_core_arena_initialize()
'-> dfb_core_initialize()
'-> dfb_core_part_initialize()
'-> dfb_screens_initialize()
'-> dfb_assertion_fail()
(!) [28359: 0.584] --> Caught signal 5 (sent by pid 28359, uid 0) <--
(-) DirectFB stack trace of 28359
'-> DirectFBCreate()
'-> dfb_core_create()
'-> fusion_arena_enter()
'-> dfb_core_arena_initialize()
'-> dfb_core_initialize()
'-> dfb_core_part_initialize()
'-> dfb_screens_initialize()
'-> dfb_assertion_fail()
'-> dfb_sig_action()
(-) DirectFB stack trace of 28361
'-> dfb_thread_main()
'-> fusion_read_loop()
(-) DirectFB stack trace of 28362
'-> dfb_thread_main()
'-> 0x40021e00 (9e00) from
/usr/local/lib/directfb-0.9.21-debug/systems/libdirectfb_fbdev.so (0x40018000)
(-) DirectFB stack trace of 28363
'-> dfb_thread_main()
(-) DirectFB stack trace of 28364
'-> dfb_thread_main()
'-> 0x422c4ed0 (ed0) from
/usr/local/lib/directfb-0.9.21-debug/inputdrivers/libdirectfb_ps2mouse.so (0x422c4000)
(-) DirectFB stack trace of 28365
'-> dfb_thread_main()
'-> 0x422bd6e0 (16e0) from
/usr/local/lib/directfb-0.9.21-debug/inputdrivers/libdirectfb_keyboard.so (0x422bc000)
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
Convergence GmbH
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-users" as subject.
