Il giorno gio, 14/07/2005 alle 09.52 -0600, Duane Wessels ha scritto: > I can (mostly) understand the RFC1035 code, but I cannot reproduce this > bug. Can you reproduce it? > > If you can get a core file and stack trace that would be helpful. > Also if you know anything about the type of nameserver that Squid > is using in this case (BIND, dnscache, etc)? > > Since the URL contains an IP address, Squid should not issue > a name-to-address DNS query. Perhaps Squid is configured to make > address-to-name (PTR) queries and this is why the rfc1035.c code > gets called for this request.
Hi Duane, one of the users that are affected by this bug managed to trace it, again using an URL with an ip address (http://193.99.144.85/). This is what backtrace printed: #0 0x400c9781 in kill () from /lib/libc.so.6 #1 0x4004ee5e in pthread_kill () from /lib/libpthread.so.0 #2 0x4004f339 in raise () from /lib/libpthread.so.0 #3 0x400cabe1 in abort () from /lib/libc.so.6 #4 0x400c3e42 in __assert_fail () from /lib/libc.so.6 #5 0x080b270d in rfc1035RRUnpack (buf=0x80f3740 "\027N\201\200", sz=68, off=0xbfff6b78, RR=0x85bb038) at rfc1035.c:410 #6 0x080b2b0c in rfc1035MessageUnpack (buf=0x80f3740 "\027N\201\200", sz=68, answer=0xbfff6ba8) at rfc1035.c:600 #7 0x08065598 in idnsGrokReply (buf=0x80f3740 "\027N\201\200", sz=68) at dns_internal.c:337 #8 0x080659f2 in idnsRead (fd=8, data=0xbfff6c30) at dns_internal.c:452 #9 0x080612bb in comm_check_incoming_poll_handlers (nfds=1, fds=0xbfff6cd0) at comm_select.c:236 #10 0x08061e1b in comm_poll_dns_incoming () at comm_select.c:900 #11 0x08061c9e in comm_poll (msec=10) at comm_select.c:484 #12 0x0807fd54 in main (argc=2, argv=0xbfffefd4) at main.c:741 Regards, -- Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]> GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
signature.asc
Description: This is a digitally signed message part
