Arch Linux

According to "man mallopt", the default behavior in case of double free corruption should be "Print detailed error message, stack trace, and memory mappings, and abort the program".

This is not the case when compiling and running a program in Arch.

For example:

$ cat toto.c
#include <stdio.h>
#include <stdlib.h>

int main(void)
{
int *a;

a = malloc(20);
free(a);
free(a);

return 0;
}
$ make toto
cc toto.c -o toto
$ ./toto
$

Worse, if I specified the value 2 to mallopt(), explicitly requiring to abort the program upon malloc errors (such a double free), nothing happens either.

$ cat toto.c
#include <malloc.h>
#include <stdio.h>
#include <stdlib.h>

int main(void)
{
int *a;

mallopt(M_CHECK_ACTION, 2);

a = malloc(20);
free(a);
free(a);

return 0;
}
$ make toto
cc toto.c -o toto
$ ./toto
$

The process should get killed by an abort signal.

Any idea what would be the cause of the program not crashing?