I don't think there's anything the client library is deliberately doing
to stop signals, but there is a problem with making PicoGUI API calls
from signal handlers. If you need to make a PicoGUI call in response to
a signal, you should set a flag in the signal handler and set up a
select() bottom-half with pgCustomizeSelect() that checks for that flag.
On 2002.01.28 08:04 hasan huseyin yilmaz wrote:
> hey
> I am trying to catch some signals which is sent by another
> process in linux system.I use linux signal handler function to set
> the interrupt vector to my functions.
>
> /* signal function in linux */
> signal(SIG_INT,(void *)interrupt);
>
> void interrupt(void)
> {
> pgMessageDialog("Signal",0,"SIG_INT signal Arrived");
> }
>
> when I compile my application there is no error.But when the signal
> arrives my application down.How can I handle signals? isnt this same
> as linux signal handling routines.
> when SIG_INT signal comes to application.my application understands
> it as an event then it calls up some event handler function then it
> is terminated.
> This is just an example of my interrupt function but it never calls
> up this interrupt function.
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp.
>
>
> _______________________________________________
> Pgui-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/pgui-devel
_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/pgui-devel
