misleading error message

[Sergey B Kirpichev]

Hello,
I believe, there is issue in the GMP, coming from changeset
changeset:   18292:0f5102b5dea7
user:        Marco Bodrato <bodrato at mail.dm.unipi.it>
date:        Sun Dec 12 14:24:10 2021 +0100
summary:     Handle overflow in mpz_type through errno.

included in 6.3.0 release.  Previously, for various cases in
mpz/init2.c, "gmp: overflow in mpz type" was printed to stderr and
abort() called.  Now GMP instead just calls  __gmp_exception(), that
raise SIGFPE and abort().  System prints something like "Floating point
exception", which might look misleading, as the program termination
actually related to memory management.

I think it's better to provide more meaningful error messages, which
will be directly set by GMP.  Like in the memory.c now.

Related gmpy2 issue (it seems that the first OP example was
with GMP<6.3 and second, for gmpy2 - with 6.3:
https://github.com/aleaxit/gmpy/issues/497
I'm not sure, howeveR, that gmpy2 extension is a right place
to address problem.

PS: posted (with help from Sage people) to gmp-discuss@ because now
I have also troubles with using public GMP mail lists and web site,
see https://github.com/aleaxit/gmpy/issues/465.

I seems the site blocks access from russian ip, is this intentional?

Posting to mail lists from @gmail.com also is impossible anymore.  Last time
I've tried: subscription was successful, but not posting.  Or this happens
only for my account (messages were from skirpichev at gmail.com)?

Now I also see "Starting in early
2024, we cannot deliver email to any gmail.com addresses."  I suspect it's
because missing DMARC policy for gmplib.org.  Why not set SPF & DMARC
for this domain?  This should fix your problems with Gmail (and, perhaps,
with more and more other email providers, which adopt similar policies).