[Dnsmasq-discuss] dnsmasq 2.86 crash

[Geert Stappers]

On Wed, Oct 13, 2021 at 09:45:30PM -0400, Eloy Paris wrote:
> On Wed, Oct 13, 2021 at 09:44:56AM +0100, Simon Kelley wrote:
> > On 13/10/2021 05:03, Eloy Paris wrote:
> > > Sorry, I forgot the backtrace; here it is:
> > > 
> > > (gdb) bt
> > > #0  0x0000561772564d46 in lookup_domain (domain=0x561772b1d7a0 "enterprise.activity.windows.com", flags=flags at entry=128,
> > >     lowout=lowout at entry=0x7ffe8a4b63ac, highout=highout at entry=0x7ffe8a4b63b0) at domain-match.c:234
> > > #1  0x0000561772532b1e in forward_query (udpfd=5, udpaddr=udpaddr at entry=0x7ffe8a4b6500, dst_addr=dst_addr at entry=0x7ffe8a4b64e0,
> > >     dst_iface=dst_iface at entry=13, header=header at entry=0x561772b1fae0, plen=plen at entry=49, limit=0x561772b1fce0 "", now=1634091453,
> > >     forward=0x0, ad_reqd=0, do_bit=0) at forward.c:258
> > > #2  0x000056177253387e in receive_query (listen=listen at entry=0x561772b1f400, now=now at entry=1634091453) at forward.c:1636
> > > #3  0x0000561772538b7c in check_dns_listeners (now=now at entry=1634091453) at dnsmasq.c:1810
> > > #4  0x000056177251888b in main (argc=<optimized out>, argv=<optimized out>) at dnsmasq.c:1237
> > > (gdb)
> > > 
> > Based on the location of the crash, and the circumstances that cause it,
> > my guess is that this will be fixed by
> > 
> > https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d290630d31f4517ab26392d00753d1397f9a4114
> > 
> > Please could you try that, and get back to us if it doesn't sort the
> > problem?
> > 
> > 
> > Cheers,
> > 
> > Simon.
> > 
> > 
> Hi Simon,

Hello Mailinglist,

 
> Glad to hear it might be a known issue.
> I'll test that patch and report back.

Do know that patch is already in git repository.
So no need reason to worry about how to apply it.

I look forward to the report back.
This email for preventing another self reply.


> Cheers,
> Eloy Paris.-


Groeten
Geert Stappers
-- 
Silence is hard to parse