GitLab

(This might be a similar issue as #1604, but with a different backtrace and that I can't reproduce it.)

I have a FreeBSD 12.1 under KVM (6 vCPU, 8 G RAM), where I triggered a core dump of named by running system test under a tight loop (e.g. while true; do make -j6 -k test V=1; done) and pressed Ctrl-C.

Here's the backtrace:

Core was generated by `/usr/home/newman/bind9/bin/named/.libs/named -D addzone-ns2 -X named.lock -m rec'.
Program terminated with signal SIGABRT, Aborted.
#0  0x0000000800e0845a in thr_kill () from /lib/libc.so.7
[Current thread is 1 (LWP 100813)]
(gdb) bt
#0  0x0000000800e0845a in thr_kill () from /lib/libc.so.7
#1  0x0000000800e06844 in raise () from /lib/libc.so.7
#2  0x0000000800d79079 in abort () from /lib/libc.so.7
#3  0x00000000002309e5 in assertion_failed (file=0x8002b45db "interfacemgr.c", line=335, type=<optimized out>, 
    cond=0x8002b67e8 "(__builtin_expect(!!((mgr) != ((void *)0)), 1) && __builtin_expect(!!(((const isc__magic_t *)(mgr))->magic == ((('I') << 24 | ('F') << 16 | ('M') << 8 | ('G')))), 1))") at ./main.c:261
#4  0x000000080070333a in isc_assertion_failed (file=0x189cd <error: Cannot access memory at address 0x189cd>, line=6, type=isc_assertiontype_require, cond=0x800e0847a <thr_self+10> "\017\202\224\064") at assertions.c:48
#5  0x00000008002ce1e3 in ns_interfacemgr_getaclenv (mgr=<optimized out>) at interfacemgr.c:335
#6  0x000000000022ec3e in address_ok (sockaddr=0x7fffdf1f6e08, acl=0x80181bb30) at controlconf.c:228
#7  0x000000000022eb12 in control_newconn (task=<optimized out>, event=<optimized out>) at controlconf.c:627
#8  0x0000000800727329 in dispatch (manager=0x801901bd0, threadid=<optimized out>) at task.c:1150
#9  0x00000008007254af in run (queuep=<optimized out>) at task.c:1340
#10 0x0000000800c32776 in ?? () from /lib/libthr.so.3
#11 0x0000000000000000 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffdf1f7000

A more detailed backtrace follows, but the core file and the named binary are gone: core.gdb.