Re: [Dnsmasq-discuss] v2.88rc2 segmentation fault with config "local=//" [PATCH]

2022-11-25 Thread Petr Menšík
Hi! After reading those changes a bit, it seems there are too many variables used in a complex mess. It is very easy to get lost in them, especially when sdetails just points somewhere to local function other variables. I made attempt to reduce the complexity and amount of local variables.

Re: [Dnsmasq-discuss] v2.88rc2 segmentation fault with config "local=//"

2022-11-17 Thread Simon Kelley
Thanks for testing these builds. That's a genuine problem. Fixed in 2.88rc3, in git now. Cheers, Simon. On 17/11/2022 18:26, Johnny S. Lee via Dnsmasq-discuss wrote: "local=//" means "Do not forward unqualified names to any upstream servers", right? It has not generated any kind of error

Re: [Dnsmasq-discuss] v2.88rc2 segmentation fault with config "local=//"

2022-11-17 Thread Johnny S. Lee via Dnsmasq-discuss
After further tests, `dnsmasq -d --local=//` OK `dnsmasq -d -H file --local=//` Segmentation fault On Fri, 18 Nov 2022 at 02:26, Johnny S. Lee <_...@jsl.io> wrote: > > "local=//" means "Do not forward unqualified names to any upstream > servers", right? > It has not generated any kind of error

[Dnsmasq-discuss] v2.88rc2 segmentation fault with config "local=//"

2022-11-17 Thread Johnny S. Lee via Dnsmasq-discuss
"local=//" means "Do not forward unqualified names to any upstream servers", right? It has not generated any kind of error until I updated to v2.88rc2. The last build I've been using was built against d3c21c596ef96027429b11216fcdbf65c9434afa ___