Per-thread FPE pointer not being initialized

David Reiss <>
Wed Jul 1 04:34:39 CEST 2009

The per-thread last floating point exception pointer is not initialized to
NULL when it is allocated.  As a result, spurious floating point
exceptions are reported.

This is 100% reproducible for me on CentOS 5.1 for x86-64, with Erlang/OTP
R13B built from source with gcc 2.5 and gcc 4.1.2.  It doesn't happen with
R13B01, but, based on the nature of the bug, I think that is most likely
due to chance.

Steps to reproduce:

1/ Start up a node with
  :~$ erl -noshell -name bob@`hostname`

2/ Build and compile test program
  :~$ cat test.erl
  start([Remote]) ->
    rpc:call(Remote, erlang, is_float, [750.0]).
  :~$ erlc test.erl

3/ Run test program
  :~$ erl -noshell -name alice@`hostname` -pz . -s test
start bob@`hostname` -s init stop

The "alice" node exits with no output.  After running the "alice" command,
the "bob" node prints the following

  ERTS_FP_CHECK_INIT at 0x4aaded: detected unhandled FPE at 0x2


diff otp_src_R13B/erts/emulator/sys/unix/sys_float.c
--- otp_src_R13B/erts/emulator/sys/unix/sys_float.c	2009-06-30
17:53:31.000000000 -0700
+++ otp_src_R13B/erts/emulator/sys/unix/sys_float.c	2009-06-30
17:53:31.000000000 -0700
@@ -57,7 +57,8 @@
 void erts_thread_init_fp_exception(void)
     unsigned long *fpe = erts_alloc(ERTS_ALC_T_FP_EXCEPTION, sizeof(*fpe));
+    *fpe = 0;
     erts_tsd_set(fpe_key, fpe);


More information about the erlang-patches mailing list