Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: neutral (herse.apache.org: 195.212.29.156 is neither permitted
 nor denied by domain of mark.hindess@googlemail.com)
Message-Id: <200705160820.l4G8KlAU014458@d12av04.megacenter.de.ibm.com>
From: "Mark Hindess" <mark.hindess@googlemail.com>
To: "Apache Harmony Dev List" <dev@harmony.apache.org>
Subject: [classlib] hy.no.sig option
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 May 2007 09:20:32 +0100


For a while now, I've been building classlib with the hy.no.sig option
to avoid the problems of both classlib and the VM trying to install
master signal handlers.  Is it time we made this the default?  Has
anyone else been testing this?

FYI: the easiest way to test it today is just doing:

  echo hy.no.sig=true >>$HOME/.harmony-classlib.properties

Of course, it really shouldn't make any practical difference since the
old classlib signal handler was only invoked in the event of a crash.

I propose we change the default from false to true.  Does this seem
reasonable?  This will mean that no handler will be registered until the
VM is initialized but I don't think this is a significant issue - since
crashes before the VM is initialized should (hopefully) be pretty rare.

Ultimately, I'd like to remove the option altogether since maintaining
duplicate signal handlers doesn't offer any significant benefits.

Regards,
 Mark.