Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > On Tue, Feb 18, 2003 at 03:35:32PM +0100, Denis Oliver Kropp wrote: > > > > As it had a segfault you should ignore subsequent error messages. > > It would help a lot if you could give us a stack trace or compile > > DirectFB with "--enable-debug", it adds assertions and some debug > > messages that may help us. > > OK. I posted, several days ago, a message with a log in it. It never > showed up. Must be a limit on the size of messages to the list and > nobody has approved it yet. Would be nice if the ML software sent > back a "your message is too big and awaits approval" type of message > or "you message is too big and was refused" message rather than it > just disappearing into thin air, but I digress.
We recently switched to ecartis, I guess it's just a question of the config. > Anyway, the latest log can be found at: > > http://brian.interlinx.bc.ca/XDirectFB-03Feb26-1.log The crash happens somewhere in dfb_surface_destroy() after the destroy notification is dispatched. If you don't want to run XDirectFB in gdb which works fine, you could add debug printf's to this function and I will have a closer look at the affected lines. -- 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-dev" as subject.
