diff options
| author | Loic Dachary <loic@dachary.org> | 2014-12-01 21:50:17 +0100 |
|---|---|---|
| committer | Loic Dachary <ldachary@redhat.com> | 2014-12-15 13:47:47 +0100 |
| commit | e7131cfd854a54e59459bc8fa1a98e867cf0ac2b (patch) | |
| tree | 058ce81b48df49ba813a34d7e213adc82dbc5d68 /NEWS | |
| parent | 70dd94ae38f2d20dd78532a6dfd1310fdfb4a884 (diff) | |
| download | gf-complete-e7131cfd854a54e59459bc8fa1a98e867cf0ac2b.tar.gz | |
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>
(cherry picked from commit 29427efac2ce362fce8e4f5f5f1030feba942b73)
Diffstat (limited to 'NEWS')
0 files changed, 0 insertions, 0 deletions