On 9/30/05, Jorge Luis Zapata Muga <[EMAIL PROTECTED]> wrote:
You could always turn on the D_DEBUG_AT messages by editing debug statements inside your directfbrc, ex:
debug = directfb # get all DFB core messages
or
debug = core/surface # just listen to surface D_DEBUG_AT messages
debug = core/layers # and the layer messages
debug = core/windows # as well as the window m essages
Best is to grep for D_DEBUG_DOMAIN instructions in the DFB sources, and look at the second parameter. Note that the string is case-insensitive in the directfbrc file, and you could also make incomplete strings that narrows down the scope of messages.
--Kent
hi all, its almost done the application i was doing with directfb. i
used the sdl backend, but now when i test it (or any other directfb
app) on the fb backend (a radeon) it hangs. is there a way to sync the
syslog so on the reboot i can see the messages and debug it (i think
you have been already in this situation)? is there any known problem
with the radeonfb?
You could always turn on the D_DEBUG_AT messages by editing debug statements inside your directfbrc, ex:
debug = directfb # get all DFB core messages
or
debug = core/surface # just listen to surface D_DEBUG_AT messages
debug = core/layers # and the layer messages
debug = core/windows # as well as the window m essages
Best is to grep for D_DEBUG_DOMAIN instructions in the DFB sources, and look at the second parameter. Note that the string is case-insensitive in the directfbrc file, and you could also make incomplete strings that narrows down the scope of messages.
--Kent
--
Something, Anything!
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
