Unbound 1.13.1 segfault

[Steven Wills]

>> Debugging old versions is waste of developer's time.
> If this is an OS-supplied Unbound, then that debug is on the OS vendor. They may be able to help.
>
> -FG

Damn, Daniel. Tell use how you really feel. Try a little politeness. 




------- Original Message -------
On Tuesday, December 20th, 2022 at 05:23, Petr Menšík via Unbound-users <unbound-users at lists.nlnetlabs.nl> wrote:


> 
> 
> On 16. 12. 22 14:40, Felipe Gasper via Unbound-users wrote:
> 
> > > On Dec 16, 2022, at 08:13, Petr Špaček via Unbound-users unbound-users at lists.nlnetlabs.nl wrote:
> > > "Upgrade."
> > > 
> > > Latest Unbound is 1.17.0 - that's far away from 1.13.1, with lots of fixes merged in meanwhile.
> > > 
> > > Debugging old versions is waste of developer's time.
> > > If this is an OS-supplied Unbound, then that debug is on the OS vendor. They may be able to help.
> > 
> > -FG
> 
> 
> We do not know what OS it is and what version it is. We may be able to
> guess, but those information should be provided instead. I agree a
> report for that crash should go to the vendor first. They may find that
> issue is still unfixed or backport existing change.
> 
> --
> Petr Menšík
> Software Engineer, RHEL
> Red Hat, http://www.redhat.com/
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB