This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: threads+CNI+SIGINT

To: Tom Tromey <tromey at cygnus dot com>
Subject: Re: threads+CNI+SIGINT
From: Jeff Sturm <jsturm at sigma6 dot com>
Date: Mon, 27 Mar 2000 12:20:40 -0500
CC: osk at hem dot passagen dot se, java-discuss at sourceware dot cygnus dot com
Organization: AppNet
References: <20000326103510.A10029@strix.eductussyd.se> <38DE3676.425F6D9A@sigma6.com> <200003271646.IAA25367@ferrule.cygnus.com>

Tom Tromey wrote:
> Jeff> SIGINT handling is necessary on Linux to ensure that all threads
> Jeff> terminate, I believe.
> 
> What is it that we'd need to do?

I haven't tested/researched the issue yet... but I've had trouble with
other linuxthreads programs before, in which sending a signal to one PID
(thread) kills that thread, leaving the process running.  (At least the
IBM JDK behaves that way.)

That's not particularly nice behavior IMHO... the runtime should either
ignore the signal, or act on all threads (i.e. by shutting down).

A SIGINT from the keyboard (^C) will be automatically sent to all
processes which share the same controlling tty, which in that case will
probably do the right thing.

-- 
Jeff Sturm
jsturm@sigma6.com

References:
- threads+CNI+SIGINT
  - From: Oskar Liljeblad
- Re: threads+CNI+SIGINT
  - From: Jeff Sturm
- Re: threads+CNI+SIGINT
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]