misleading error message
Sergey B Kirpichev
skir at sagemath.org
Tue Sep 24 11:34:05 CEST 2024
On Tue, Sep 24, 2024 at 10:44:48AM +0200, Vincent Lefevre wrote:
> It will not do both in general. The "raise (SIGFPE);" will normally
> terminate the process with a core dump. The abort() will be called
> only if SIGFPE is ignored, but it is dangerous to ignore this signal
No. If signal handler set - the raise() function shall not return until
after the signal handler does. But then abort() will be called.
So, in quoted issue OP got from OS something like from this toy case,
not a core dump at all:
sk at note:~ $ cat a.c
#include <signal.h>
#include <stdlib.h>
int main(void)
{
raise(SIGFPE);
abort();
return 0;
}
sk at note:~ $ cc a.c && ./a.out
Floating point exception
> > 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).
>
> This is a stupid requirement from Gmail, in particular for users
> of multiple machines and/or mailing-lists (one has to use "all"
> for SPF, which is misleading).
I don't see reasons to use "all" for mailing-lists. See e.g. gnu.org.
More information about the gmp-discuss
mailing list