Re: [Dnsmasq-discuss] segv using 2.75 with dnssec

Hi Simon, On Tue, Dec 8, 2015 at 12:08 AM, Simon Kelley wrote: > I think the problem may be the code-path in get_new_frec() which frees > old frecs. Warping the time will make all the records suddenly old, > and they'll get freed by the loop. The problem is that some

Re: [Dnsmasq-discuss] [PATCH] Treat records signed using unknown algorithms as unsigned instead of bogus

> I wish I was on firmer ground than I am in arguing this. Nevertheless, > if we keep going, we might be able to reach the conclusion. > > > Let's start with a concrete example: > > srk@holly:~/dnsmasq/dnsmasq$ dig @8.8.8.8 +dnssec isc.org > > ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> @8.8.8.8

Re: [Dnsmasq-discuss] segv using 2.75 with dnssec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Staring at the code some more, I'm less sure I've found the problem. If it breaks again, running a backtrace (bt command) would be useful. Cheers, Simon. On 08/12/15 07:48, Andre Heider wrote: > Hi Simon, > > On Tue, Dec 8, 2015 at 12:08 AM,

Re: [Dnsmasq-discuss] segv using 2.75 with dnssec

Hi, On Tue, Dec 8, 2015 at 5:33 PM, Simon Kelley wrote: > Staring at the code some more, I'm less sure I've found the problem. free_frec looks like this now: static void free_frec(struct frec *f) { if (f->sentto == NULL) { my_syslog(LOG_WARNING, "free_frec