[FreeTDM] Fix a couple of ftdm_log() format string errors.
... that could cause segmentation faults. Caught while working on __check_printf() support for ftdm_log(). Signed-off-by: Stefan Knoblich <stkn@openisdn.net>
This commit is contained in:
parent
124c04624a
commit
9d5eb0737b
|
@ -255,7 +255,8 @@ FT_DECLARE (int) ftdm_config_get_cas_bits(char *strvalue, unsigned char *outbits
|
||||||
if ('1' == cas_bits[x]) {
|
if ('1' == cas_bits[x]) {
|
||||||
*outbits |= bit;
|
*outbits |= bit;
|
||||||
} else if ('0' != cas_bits[x]) {
|
} else if ('0' != cas_bits[x]) {
|
||||||
ftdm_log(FTDM_LOG_ERROR, "Invalid CAS pattern specified: %s, just 0 or 1 allowed for each bit\n");
|
ftdm_log(FTDM_LOG_ERROR, "Invalid CAS pattern specified: %s, just 0 or 1 allowed for each bit\n",
|
||||||
|
strvalue);
|
||||||
return -1;
|
return -1;
|
||||||
}
|
}
|
||||||
bit >>= 1;
|
bit >>= 1;
|
||||||
|
|
|
@ -472,7 +472,7 @@ FT_DECLARE(ftdm_status_t) ftdm_interrupt_signal(ftdm_interrupt_t *interrupt)
|
||||||
* otherwise users that never call interrupt wait eventually will
|
* otherwise users that never call interrupt wait eventually will
|
||||||
* eventually have the pipe buffer filled */
|
* eventually have the pipe buffer filled */
|
||||||
if ((err = write(interrupt->writefd, "w", 1)) != 1) {
|
if ((err = write(interrupt->writefd, "w", 1)) != 1) {
|
||||||
ftdm_log(FTDM_LOG_ERROR, "Failed to signal interrupt: %s\n", errno, strerror(errno));
|
ftdm_log(FTDM_LOG_ERROR, "Failed to signal interrupt: %s\n", strerror(errno));
|
||||||
return FTDM_FAIL;
|
return FTDM_FAIL;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue