patches/uClibc/0.9.29/130-fix-gethostent_r-failure-retval.patch
author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Tue May 08 18:31:10 2012 +0200 (2012-05-08) |
changeset 2964 |
d48c03998dc1 |
parent 108 |
69407950a2a2
|
permissions |
-rw-r--r-- |
scripts: fix catching failures
POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).
bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
yann@108
|
1 |
diff -ur uClibc-0.9.29/libc/inet/resolv.c uClibc-0.9.29-patched/libc/inet/resolv.c
|
yann@108
|
2 |
--- uClibc-0.9.29/libc/inet/resolv.c 2007-04-23 12:01:05.000000000 -0500
|
yann@108
|
3 |
+++ uClibc-0.9.29-patched/libc/inet/resolv.c 2007-05-09 18:05:33.563404419 -0500
|
yann@108
|
4 |
@@ -1700,7 +1700,7 @@
|
yann@108
|
5 |
int gethostent_r(struct hostent *result_buf, char *buf, size_t buflen,
|
yann@108
|
6 |
struct hostent **result, int *h_errnop)
|
yann@108
|
7 |
{
|
yann@108
|
8 |
- int ret;
|
yann@108
|
9 |
+ int ret = HOST_NOT_FOUND;
|
yann@108
|
10 |
|
yann@108
|
11 |
__UCLIBC_MUTEX_LOCK(mylock);
|
yann@108
|
12 |
if (__gethostent_fp == NULL) {
|