From: "James S. Rogers" <jimmaureenrogers@worldnet.att.net>
Subject: Re: tasking programs built with GNAT insensitive to SIGTERM
Date: Wed, 29 Jan 2003 20:06:53 GMT
Date: 2003-01-29T20:06:53+00:00 [thread overview]
Message-ID: <xvWZ9.10503$rq4.796488@bgtnsc05-news.ops.worldnet.att.net> (raw)
In-Reply-To: mailman.12.1043862309.30820.comp.lang.ada@ada.eu.org
"David C. Hoos" <david.c.hoos.sr@ada95.com> wrote in message
news:mailman.12.1043862309.30820.comp.lang.ada@ada.eu.org...
>
> ----- Original Message -----
> From: "Oliver Kellogg" <okellogg@freenet.de>
> Newsgroups: comp.lang.ada
> To: <comp.lang.ada@ada.eu.org>
> Sent: Wednesday, January 29, 2003 9:04 AM
> Subject: tasking programs built with GNAT insensitive to SIGTERM
>
>
> > Hi,
> >
> > Under Linux, how come tasking programs built with GNAT
> > (3.2, but other versions as well) don't react to
> > "kill -TERM" ?
>
> Have you tried kill -KILL? Is it possible that the tasking runtime is
> setting the program up to ignore SIGTERM?
>
> Another possibility is that because GNAT tasking is using Linux
> threads, not all threads are receiving the signal. You can insure
> that all signals in a process group receive a signal by specifying
> the negative of the process group id in place of the process id
> in the kill command.
>
> David
> >
> > Is there a trick to make them killable?
> >
> > See also http://gcc.gnu.org/cgi-bin/gnatsweb.pl,
> > bug number 9480.
> >
> > Thanks,
> >
> > Oliver
A discussion of signals and Linux Threads on comp.programming.threads
indicates that Linux Threads are broken regarding handling signals.
This appears to have revealed the same weakness.
Jim Rogers
next prev parent reply other threads:[~2003-01-29 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 15:04 tasking programs built with GNAT insensitive to SIGTERM Oliver Kellogg
2003-01-29 17:45 ` David C. Hoos
2003-01-29 20:06 ` James S. Rogers [this message]
2003-01-29 21:54 ` Mark Johnson
2003-02-04 19:55 ` Craig Carey
2003-02-04 21:35 ` Mark Johnson
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox