This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: How to test a patch in resolv/?
- From: Marko Myllynen <myllynen at redhat dot com>
- To: Stan Shebs <stanshebs at google dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Wed, 7 Oct 2015 13:33:26 +0300
- Subject: Re: How to test a patch in resolv/?
- Authentication-results: sourceware.org; auth=none
- References: <CA+5-Q5KH4NS8V8GPX0YeQwq59UHWSn7eimmbZ=47jhJae5oqLA at mail dot gmail dot com>
- Reply-to: myllynen at redhat dot com
Hi,
On 2015-10-06 21:38, Stan Shebs wrote:
> Last week at Google, getaddrinfo() blew up in an attention-getting way,
> apparently due to an innocuous internal server change triggering BZ 16754
> (the library version we're using derives from 2.19).
>
> So while there is a patch for this bug, and it even applies cleanly to our
> version, I'm wondering how to write a test that demonstrates it's an actual
> fix, without depending on masses of internal Google configuration. It seems
> like one ought to be able to build a little mock DNS server, but I don't see
> that anyone has done that to date, and maybe there is some better way
> to do a unit test.
>
> Does anybody have any ideas or suggestions? Thanks!
I think cwrap is worth mentioning here:
https://cwrap.org/
https://cwrap.org/resolv_wrapper.html
Cheers,
--
Marko Myllynen