knotc zone-reload and crash
When using knotc zone-reload, accidental program crashes may occur. The following is detailed information:
knot version: 3.0.1 the core file info:
warning: Unexpected size of section `.reg-xstate/189700' in core file.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/opt/knot/sbin/knotd -c /opt/etc/knot/knot.conf -d'.
Program terminated with signal SIGSEGV, Segmentation fault.
warning: Unexpected size of section `.reg-xstate/189700' in core file.
#0 0x00007fa3cf4b3d05 in knot_dname_labels (name=name@entry=0x40 <error: Cannot access memory at address 0x40>,
pkt=pkt@entry=0x0) at libknot/dname.c:751
751 libknot/dname.c: No such file or directory.
[Current thread is 1 (Thread 0x7e40b6df4700 (LWP 189700))]
(gdb) bt
#0 0x00007fa3cf4b3d05 in knot_dname_labels (name=name@entry=0x40 <error: Cannot access memory at address 0x40>,
pkt=pkt@entry=0x0) at libknot/dname.c:751
#1 0x00007fa3cf4b4430 in knot_dname_in_bailiwick (name=name@entry=0x7e40540008cc "\003abc\atestdns\003com",
bailiwick=0x40 <error: Cannot access memory at address 0x40>) at libknot/dname.c:802
#2 0x000055c024e6eeaf in zone_contents_find_dname (zone=0x7e40a80e7010, name=0x7e40540008cc "\003abc\atestdns\003com",
match=0x7e3fafaab358, closest=0x7e3fafaab360, previous=0x7e3fafaab368) at knot/zone/contents.c:297
#3 0x000055c024ec298d in solve_name (state=0, pkt=0x7e3fafaab560, qdata=0x7e3fafaab038) at knot/nameserver/internet.c:405
#4 0x000055c024ec2fdc in solve_answer (ctx=0x0, qdata=0x7e3fafaab038, pkt=0x7e3fafaab560, state=<optimized out>)
at knot/nameserver/internet.c:441
#5 answer_query (qdata=0x7e3fafaab038, pkt=0x7e3fafaab560) at knot/nameserver/internet.c:700
#6 internet_process_query (pkt=pkt@entry=0x7e3fafaab560, qdata=0x7e3fafaab038) at knot/nameserver/internet.c:767
#7 0x000055c024ea4a93 in query_internet (ctx=0x7e40b6df3a90, pkt=0x7e3fafaab560) at knot/nameserver/process_query.c:150
#8 process_query_out (ctx=0x7e40b6df3a90, pkt=0x7e3fafaab560) at knot/nameserver/process_query.c:637
#9 0x000055c024e6c99a in knot_layer_produce (pkt=0x7e3fafaab560, ctx=0x7e40b6df3a90) at ./knot/query/layer.h:134
#10 udp_handle (xdp_msg=0x0, tx=0x7fa3a8002a40, rx=0x7fa3a8002720, ss=0x7fa3a8002040, fd=<optimized out>, udp=0x7e40b6df3a90)
at knot/server/udp-handler.c:169
#11 udp_recvmmsg_handle (ctx=ctx@entry=0x7e40b6df3a90, d=d@entry=0x7fa3a8002038, unused=unused@entry=0x0)
at knot/server/udp-handler.c:404
#12 0x000055c024e6ce91 in udp_master (thread=thread@entry=0x55c026aca740) at knot/server/udp-handler.c:689
#13 0x000055c024e68a65 in thread_ep (data=0x55c026aca740) at knot/server/dthreads.c:146
#14 0x00007fa3ce5a44a4 in start_thread (arg=0x7e40b6df4700) at pthread_create.c:456
#15 0x00007fa3cd42bd0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
Could you provide some suggestions? What may be the problem causing it?