I tried to replicate it with this patch to the test suite:
diff --git a/resolv/tst-bug18665-tcp.c b/resolv/tst-bug18665-tcp.c
index 9b1ff0fbd8..e8e0d12bb7 100644
--- a/resolv/tst-bug18665-tcp.c
+++ b/resolv/tst-bug18665-tcp.c
@@ -47,6 +47,41 @@ response (const struct resolv_response_context *ctx,
Thanks for the update. A packet capture could still be useful, and also
a backtrace (with symbols) from the crash.
We have an upstream test case which is supposed to cover various packet
sizes, and I am going to try to adopt it to cover this. The code itself
is pretty much impenetrable. We have
In trying to do the work requested for the report, it took a different
turn. General sequence is still correct, with the following caveat:
- our DNS server added a CNAME record to the truncated UDP reply,
bringing the size to over 512 bytes
The response is well formed, just too big. Since
Would you be able to share packet capture (tcpdump -s 0 -w CAPTURE-FILE,
and then the output of CAPTURE-FILE)? Thanks.
As far as I can tell, “getent ahosts large-a.t.enyo.de” results in DNS
activity that matches the preconditions in your description, but I don't
observe a crash (even with Ubuntu
