Signals SIGSTOP

2000-06-12 Thread Nuno Almeida
I would like to know if this is simply a singularity of Debian, or if it's a bug of mine. When I'm programming in C/C++ to other linuxdistr. and Imake a signal trap I can't, and that's absolutly normal, trap the signals 9 and 17, for SIGKILL and SIGSTOP. On Debian I can catch the SIGSTOP

Fw: Signals SIGSTOP

2000-06-12 Thread Nuno Almeida
I would like to know if this is simply a singularity of Debian, or if it's a bug of mine. When I'm programming in C/C++ to other linuxdistr. and Imake a signal trap I can't, and that's absolutly normal, trap the signals 9 and 17, for SIGKILL and SIGSTOP. On Debian I can catch the SIGSTOP

Re: Signals SIGSTOP

2000-06-12 Thread kmself
On Mon, Jun 12, 2000 at 02:40:16AM +0100, Nuno Almeida wrote: I would like to know if this is simply a singularity of Debian, or if it's a bug of mine. When I'm programming in C/C++ to other linux distr. and I make a signal trap I can't, and that's absolutly normal, trap the signals 9 and

Re: Signals SIGSTOP

2000-06-12 Thread Chris Gray
On Mon, Jun 12, 2000 at 02:40:16AM +0100, Nuno Almeida wrote: I would like to know if this is simply a singularity of Debian, or if it's a bug of mine. When I'm programming in C/C++ to other linux distr. and I make a signal trap I can't, and that's absolutly normal, trap the signals 9 and

Re: Signals SIGSTOP

2000-06-12 Thread Brad
Please break your lines at 76 characters. On Mon, Jun 12, 2000 at 02:40:16AM +0100, Nuno Almeida wrote: I would like to know if this is simply a singularity of Debian, or if it's a bug of mine. When I'm programming in C/C++ to other linux distr. and I make a signal trap I can't, and that's