pastebin - collaborative debugging tool
rovema.kpaste.net RSS


SIGFPE codes / Untitled
Posted by Anonymous on Tue 24th Aug 2021 14:02
raw | new post

  1. 14:47:36.354  [1555 init_rds]; [INFO] StdSignalHandler got signal 8 number 1
  2. 14:47:36.358  [1555 init_rds]; [ERROR] 3: linux-gate.so.1(__kernel_rt_sigreturn+0) [0xb7f8f570] (-2)
  3.  
  4. see siginfo_t(3) and /usr/include/asm-generic/siginfo.h
  5.  
  6.    198  /*
  7.    199   * SIGFPE si_codes
  8.    200   */
  9.    201  #define FPE_INTDIV      1       /* integer divide by zero */
  10.    202  #define FPE_INTOVF      2       /* integer overflow */
  11.    203  #define FPE_FLTDIV      3       /* floating point divide by zero */
  12.    204  #define FPE_FLTOVF      4       /* floating point overflow */
  13.    205  #define FPE_FLTUND      5       /* floating point underflow */
  14.    206  #define FPE_FLTRES      6       /* floating point inexact result */
  15.    207  #define FPE_FLTINV      7       /* floating point invalid operation */
  16.    208  #define FPE_FLTSUB      8       /* subscript out of range */
  17.    209  #define __FPE_DECOVF    9       /* decimal overflow */
  18.    210  #define __FPE_DECDIV    10      /* decimal division by zero */
  19.    211  #define __FPE_DECERR    11      /* packed decimal error */
  20.    212  #define __FPE_INVASC    12      /* invalid ASCII digit */
  21.    213  #define __FPE_INVDEC    13      /* invalid decimal digit */
  22.    214  #define FPE_FLTUNK      14      /* undiagnosed floating-point exception */
  23.    215  #define FPE_CONDTRAP    15      /* trap on condition */
  24.    216  #define NSIGFPE         15

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}




All content is user-submitted.
The administrators of this site (kpaste.net) are not responsible for their content.
Abuse reports should be emailed to us at