res_state and res_init definition order in resolv.c
Eugene Rudoy
gene.devel at gmail.com
Sat Jul 13 11:17:25 UTC 2013
Hi all,
could someone who is familiar with resolv.c and understands all its res_init
related tricks please comment the following two commits:
[1] "resolv.c: add support for per thread
res_state"<http://git.uclibc.org/uClibc/commit/libc/inet/resolv.c?id=aab4df0fb51660300559f5f29290709db2f7bfee>.
Note
the comment it contains "This needs to be after the use of _res in
res_init, above."
and
[2] "inet/resolv: add res_ninit and
res_nclose"<http://git.uclibc.org/uClibc/commit/libc/inet/resolv.c?id=7f74de5d4d6d10baafab4b37bb3d472f5c5f0e8c>.
This
moves res_init after the definition of _res/__resp without modifying the
comment from [1] and without explaining whether it still applies or not.
The question arises in the context of understanding whether the patch
provided in OpenWRT ticket 11929 <https://dev.openwrt.org/ticket/11929> is
a correct one and why it works for some people and doesn't work for the
other ones.
Thanks a lot!
Best,
Gene
More information about the uClibc
mailing list