GitLab

This command crashes:

> dig +nssearch grainy.io
netmgr/netmgr.c:1703: REQUIRE((((handle) != ((void *)0) && ((const isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H') << 8 | ('D')))) && __extension__ ({ __auto_type __atomic_load_ptr = (&(handle)->references); __typeof__ ((void)0, *__atomic_load_ptr) __atomic_load_tmp; __atomic_load (__atomic_load_ptr, &__atomic_load_tmp, (5)); __atomic_load_tmp; }) > 0)) failed, back trace
/lib64/libisc-9.18.3.so(+0x37f80)[0x7f072c360f80]
/lib64/libisc-9.18.3.so(isc_assertion_failed+0xc)[0x7f072c3607ec]
/lib64/libisc-9.18.3.so(isc__nmhandle_attach+0x63)[0x7f072c34b323]
dig(+0x10310)[0x55e2a9ac7310]
dig(+0x146f4)[0x55e2a9acb6f4]
dig(+0x15588)[0x55e2a9acc588]
/lib64/libisc-9.18.3.so(isc__nm_async_sendcb+0x94)[0x7f072c350584]
/lib64/libisc-9.18.3.so(isc__nm_sendcb+0xf0)[0x7f072c350710]
/lib64/libuv.so.1(+0x229ac)[0x7f072be629ac]
/lib64/libuv.so.1(uv_run+0x135)[0x7f072be4fee5]
/lib64/libisc-9.18.3.so(+0x2c464)[0x7f072c355464]
/lib64/libisc-9.18.3.so(isc__trampoline_run+0x15)[0x7f072c384c85]
/lib64/libc.so.6(+0xa7767)[0x7f072bf1a767]
/lib64/libc.so.6(+0x131c10)[0x7f072bfa4c10]
Aborted (core dumped)

I have tried with other domain names, both existing and nonexistent, and I get no output whatsoever instead. I think that's a bug too, as I don't think no-output-whatsoever is ever an acceptable outcome under any circumstances, but I haven't read the entire manual so I'm not 100% sure. What I'm 100% sure of is that when it crashes with a core dump, there's certainly a bug. If I'm using the command incorrectly I should get an error message telling me what I'm doing wrong, and if there's an issue with the specific domain it should tell me what kind of issue.

In this particular case, this is a domain I own myself for which I have changed the NS records minutes ago and the change is still propagating, so there's a possibility that the output will change in a few hours and it may no longer reproduce the issue (maybe reproducing the no-output issue instead). Or maybe not. Also that may or may not be related to what triggers the issue.