The reason is that the application process doesn't handle the signal which you are sending. If you see, the DFB application typically waits in a loop for some events. On receiving the signal, it should gracefully come out of the loop and free all the resources. You probably should handle appropriate events in the application itself.
On Wed, Dec 10, 2008 at 3:41 AM, Chris Triebel <[EMAIL PROTECTED]> wrote: > I'm writing a directfb (1.3.0) based program for an ARM board running linux > 2.6.18. > > I'm having an issue where if I kill or ^C my program the program doesn't > die. One of the threads remains behind. I get the message as shown below. > > # kill 954 > # (!) [ 954: 0.000] --> Caught signal 15 (sent by pid 54, uid 0) <-- > > Now if I kill it again I get an actual termination. > > # # kill 954 > # (!) [ 954: 4.510] --> Caught signal 15 (sent by pid 54, uid 0) <-- > > [1] 954 Terminated ./analyzer.1 > # > > > I've found that df_dok (from directfb examples 0.9.25) doesn't have this > issue, but df_window does. The latter makes sense to me since that source > was the example I started my own program from. > > Any help would be appreciated. > > > > > _______________________________________________ > directfb-users mailing list > directfb-users@directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users > > -- --------------- Thanks Amarinder
_______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
