public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Haley <aph@cambridge.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: Mon, 19 Aug 2002 03:26:00 -0000 [thread overview] Message-ID: <20020819091602.1254.qmail@sources.redhat.com> (raw) The following reply was made to PR libgcj/7532; it has been noted by GNATS. From: Andrew Haley <aph@cambridge.redhat.com> To: tromey@redhat.com Cc: <jmr@fulcrummicro.com>, gcc-gnats@gcc.gnu.org Subject: Re: libgcj/7532: shutdown hooks not run upon abnormal termination Date: Mon, 19 Aug 2002 10:08:29 +0100 (BST) Tom Tromey writes: > 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 think it's legal to do this from a signal handler. However, we might deadlock if a thread is inside a synchronized region at the time the ctrl-C is caught. We could perhaps solve this by sending a message to a dedicated shutdown thread instead of quitting immediately but I don't know if the extra complexity can be justified. However, we must ensure that if a second ctrl-C is received we terminate immediately. > I also don't think we need a gij command-line argument to reduce > signal usage. I agree. Andrew.
next reply other threads:[~2002-08-19 9:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-19 3:26 Andrew Haley [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-16 15:26 Tom Tromey 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=20020819091602.1254.qmail@sources.redhat.com \ --to=aph@cambridge.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: linkBe 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).