[ldns-users] ldns_resolver_new_frm_fp_l() comment lines bug

[Zbynek Michl]

Hi Wouter,

if I have in my resolv.conf:

#nameserver 127.0.0.1
nameserver 172.20.20.40

-> reads no resolver (error)

So at least this bug still persists in r3283.

Regards,
Zbynek

On 18.3.2010 16:40, W.C.A. Wijngaards wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Zbynek,
>
> Fixed in svn r 3210
>
> The example you gave did not fail for me?  It failed with different
> whitespace.  But anyway, the comment handling did not properly handle
> skipping onto the next line, so I fixed that :-)
>
> Thanks for the report!
>     Wouter
>
> On 03/18/2010 02:39 PM, Zbynek Michl wrote:
>> there is probably a bug in ldns_resolver_new_frm_fp_l() function. When I
>> use ldns_resolver_new_frm_file() to read /etc/resolv.conf, it
>> incorrectly handles comment lines.
>>
>> So it seems if some line is commented out, then the next line is ommited
>> too.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuiSVsACgkQkDLqNwOhpPiHrgCeKKQ1fV5Oa3m2JC1XCEiSGJmW
> r0IAnAxa2XF4C5PUzj76+qdK3v22Y746
> =xDkF
> -----END PGP SIGNATURE-----
> _______________________________________________
> ldns-users mailing list
> ldns-users at open.nlnetlabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/ldns-users