Re: CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

On Fri, 10 Dec 2021 19:41:07 +1030
Daniel O'Connor via freebsd-current <freebsd-current@freebsd.org> wrote:

> > On 25 Nov 2021, at 18:50, FreeBSD User <freebsd@walstatt-de.de> wrote:
> > 
> > Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov 22
> > 18:17:54 CET 2021 amd64) troubles me with our DNS server/service.
> > Aproximately the same time we switched on CURRENT to the CURRENT LLVM13 version and
> > also, after the compilation of a fresh OS with LLVM13, the upgrade from bind-9.16.22
> > to bind-9.16.23 took place as well as ASLR being the default.
> > 
> > Since then named is crashing with a mysterious segmentation fault (see PR 259921,
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259921).
> > 
> > Disabling ASLR as recommended to check whether ASLR triggers the SegFault did not
> > solve the problem, so I suspect a miscompilation due to llvm13.
> > 
> > On 13-STABLE bind-9.16.23 seem not to have this behaviour.
> > 
> > I'm floating like a dead man in the water, can someone help?  
> 
> lang/sdcc also seg faults (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260303),
> although there disabling ASLR via proccontrol does fix it.
> 
> Can you show a stacktrace for your seg fault?

Hello.
I have to prepare the boxes for debugging first, we switched everything off including
core dumping.

In the meanwhile, bind-9.16.24_1 has been issued in ports - the same problem occurs with
that version, too, when compiled with llvm13.


Kind regards,

O. Hartmann
> --
> Daniel O'Connor
> "The nice thing about standards is that there
> are so many of them to choose from."
>  -- Andrew Tanenbaum
> 
>