content-type: text/plain; charset="utf-8"
Content-Disposition: inline
X-RT-Original-Encoding: us-ascii
Content-Length: 1333

There is another unrelated crash on the Arch ticket for RT#35968:

https://bugs.archlinux.org/task/40304#comment122853

This one seems to be in the config parser:

May 12 23:32:34 amish named[1755]: parser.c:315: REQUIRE(tupleobj != ((void *)0) && tupleobj->type->rep == &cfg_rep_tuple) failed, back trace
May 12 23:32:34 amish named[1755]: #0 0x433afd in ??
May 12 23:32:34 amish named[1755]: #1 0x7f36c3ca515a in ??
May 12 23:32:34 amish named[1755]: #2 0x7f36c411b8ce in ??
May 12 23:32:34 amish named[1755]: #3 0x4184d8 in ??
May 12 23:32:34 amish named[1755]: #4 0x418e8a in ??
May 12 23:32:34 amish named[1755]: #5 0x419d9f in ??
May 12 23:32:34 amish named[1755]: #6 0x44ec21 in ??
May 12 23:32:34 amish named[1755]: #7 0x44fbf4 in ??
May 12 23:32:34 amish named[1755]: #8 0x7f36c3cc74dc in ??
May 12 23:32:34 amish named[1755]: #9 0x7f36c3877124 in ??
May 12 23:32:34 amish named[1755]: #10 0x7f36c303f4bd in ??
May 12 23:32:34 amish named[1755]: exiting (due to assertion failure)
May 12 23:32:34 amish systemd[1]: named.service: main process exited, code=killed, status=6/ABRT
May 12 23:32:34 amish systemd[1]: named.service: control process exited, code=exited status=1

Again, having symbol names would have been helpful. I've registered on
the Arch bug tracker and added comments asking for usable backtraces.

		Mukund