diff options
| author | Ga?l PORTAY <gael.portay@gmail.com> | 2015-05-02 11:26:22 +0200 |
|---|---|---|
| committer | Ga?l PORTAY <gael.portay@gmail.com> | 2015-05-02 11:26:22 +0200 |
| commit | f5855dcde763d77cf996a6314724cedae0e4641a (patch) | |
| tree | e32a5a3afa1c14bcec2b41a41bdac129a4381609 /libtomcrypt | |
| parent | 644a97f38af846ba4ce0172f23a01d8c1c9957e7 (diff) | |
| download | dropbear-f5855dcde763d77cf996a6314724cedae0e4641a.tar.gz | |
Uses abort() instead of raising a SIGABRT signal [-Werror]
error: ?noreturn? function does return [-Werror]
abort() is a noreturn function while raise() is not.
And because crypt_argchk() is flagged as __attribute__(noreturn), abort()
appears to be a better condidate.
This compilation warning has probably been introduced by commit
1809f741cba865b03d4db5c4ba8c41364a55d6bc.
Diffstat (limited to 'libtomcrypt')
| -rw-r--r-- | libtomcrypt/src/misc/crypt/crypt_argchk.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libtomcrypt/src/misc/crypt/crypt_argchk.c b/libtomcrypt/src/misc/crypt/crypt_argchk.c index c6675ef..a6d2a48 100644 --- a/libtomcrypt/src/misc/crypt/crypt_argchk.c +++ b/libtomcrypt/src/misc/crypt/crypt_argchk.c @@ -21,7 +21,7 @@ void crypt_argchk(char *v, char *s, int d) { fprintf(stderr, "LTC_ARGCHK '%s' failure on line %d of file %s\n", v, d, s); - (void)raise(SIGABRT); + abort(); } #endif |