DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 529EGxJ91976355
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2FAA43858D1E
To: cygwin@cygwin.com, camm@maguirefamily.org
Subject: GCL and dependencies on cygwin
Date: Sun, 09 Mar 2025 10:16:28 -0400
Message-ID: <87wmcyi91f.fsf@glory.maguirefamily.org>
MIME-Version: 1.0
From: Camm Maguire via Cygwin <cygwin@cygwin.com>
Reply-To: Camm Maguire <camm@maguirefamily.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

Greetings, and thank you all for your work on this system.

1) I am preparing a set of GCL releases, both of which basically work on
latest cygwin, but the signal handling seems to have been recently
broken.  Specifically, GCL can trap and handle SIGFPE when these
exceptions are enabled.  Under gdb, the signal appears, but then a
SIGTRAP is caught in kernel.dll under secure_getenv(), and the handler
is never called.  Thoughts?

2) I am considering volunteering as a maintainer.  I see the docs
describing the procedure.  I maintain some packages for Debian, and
wondering if there was any simplification in avoiding duplicate work
here.

Take care,
-- 
Camm Maguire			     		    camm@maguirefamily.org
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple