Package: w3m Version: 0.5.3-4 Severity: minor I just wanted to visit an https site using w3m and found a segmentation fault. It dereferences a NULL pointer, but the traceback is not useful without debugging symbols. Looking at strace I can see that it happens during (or after) DNS resolution. Oh my domain name does not resolve. Actually it only segfaults when passing a non-resolving name and using https simultaneously. alphascorpii tried this as well and her i386 w3m 0.5.3-4 does not segfault in this case. So maybe it is due to my local dns cache? Disabling my dns cache (so we both use the same dns server) and w3m keeps segfaulting on my system. Strange. No clue what goes wrong here. I'm using systemd btw. Can I check anything else?
If anyone reads this bug report and is able to reproduce it, please respond. Helmut -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-rc5-amd64 (SMP w/2 CPU cores) Locale: LANG=C Shell: /bin/sh linked to /bin/dash Versions of packages w3m depends on: ii libc6 2.13-21 ii libgc1c2 1:7.1-8 ii libgpm2 1.20.4-4 ii libncurses5 5.9-4 ii libssl1.0.0 1.0.0e-3 ii libtinfo5 5.9-4 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages w3m recommends: ii ca-certificates 20111025 Versions of packages w3m suggests: pn man-db 2.6.0.2-3 pn menu 2.1.46 pn migemo <none> pn mime-support 3.51-1 pn w3m-el <none> pn w3m-img <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
