gf-complete/src
Loic Dachary 29427efac2 use assert(0) instead of exit(1)
When a fatal error (unaligned memory etc.) is detected, gf-complete should
assert(3) instead of exit(3) to give a chance to the calling program to
catch the exception and display a stack trace. Although it is possible
for gdb to display the stack trace and break on exit, libraries are not
usually expected to terminate the calling program in this way.

Signed-off-by: Loic Dachary <loic@dachary.org>
2014-12-02 00:27:27 +01:00
..
neon arm: NEON optimisations for gf_w64 2014-10-24 14:54:55 +02:00
Makefile.am arm: NEON optimisations for gf_w64 2014-10-24 14:54:55 +02:00
gf.c use assert(0) instead of exit(1) 2014-12-02 00:27:27 +01:00
gf_general.c use assert(0) instead of exit(1) 2014-12-02 00:27:27 +01:00
gf_method.c simd: rename the region flags from SSE to SIMD 2014-10-09 23:22:32 +02:00
gf_rand.c Setting up autoconf/automake for GF-Complete 2013-12-04 21:24:29 -08:00
gf_w4.c arm: NEON optimisations for gf_w4 2014-10-24 14:53:12 +02:00
gf_w8.c use assert(0) instead of exit(1) 2014-12-02 00:27:27 +01:00
gf_w16.c arm: NEON optimisations for gf_w16 2014-10-24 14:53:57 +02:00
gf_w32.c arm: NEON optimisations for gf_w32 2014-10-24 14:54:27 +02:00
gf_w64.c arm: NEON optimisations for gf_w64 2014-10-24 14:54:55 +02:00
gf_w128.c simd: rename the region flags from SSE to SIMD 2014-10-09 23:22:32 +02:00
gf_wgen.c prefer uint8_t to char in pointer arithmetic 2014-04-10 17:21:38 +02:00