public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/7532: shutdown hooks not run upon abnormal termination
Date: Fri, 16 Aug 2002 15:26:00 -0000	[thread overview]
Message-ID: <20020816220601.8859.qmail@sources.redhat.com> (raw)

The following reply was made to PR libgcj/7532; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: <jmr@fulcrummicro.com>
Cc: gcc-gnats@gcc.gnu.org, Andrew Haley <aph@redhat.com>
Subject: Re: libgcj/7532: shutdown hooks not run upon abnormal termination
Date: 16 Aug 2002 16:02:16 -0600

 jmr> 	Shutdown hooks added with Runtime.addShutdownHook() are not run
 jmr>         if the program terminates abnormally, ie due to Ctrl-C.
 
 Yeah, definitely a bug.
 
 jmr> Here's a patch that installs a signal handler to catch SIGHUP, SIGINT, and
 jmr> SIGTERM.  The handler calls System.exit() so the shutdown hooks run.
 jmr> Installation of the signal handlers can be disabled with
 jmr> --reduce-signal-usage.
 
 I don't think we can do this stuff directly from the signal handler.
 I'm not sure what a better approach is though.  Maybe Andrew has an idea.
 
 I also don't think we need a gij command-line argument to reduce
 signal usage.
 
 Tom


             reply	other threads:[~2002-08-16 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 15:26 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-19  3:26 Andrew Haley
2002-08-07 16:36 Jesse Rosenstock
2002-08-07 16:26 Andrew Pinski
2002-08-07 16:16 jmr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020816220601.8859.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).