On 09/03/2025 14:16, Camm Maguire via Cygwin wrote:
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.
We are, as always, short of package maintainers, so this would be very
welcome.
I'm not sure what simplifications you are thinking of?
(Whilst it's probably pretty straightforward (for a person) to translate
a debian control file into a cygport file, I don't think it's likely to
be automateable)
--
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
