Kurt Roeckx <[EMAIL PROTECTED]> writes: > On Wed, Sep 24, 2008 at 08:05:24PM +0200, Andreas Metzler wrote: >> On 2008-09-23 Kurt Roeckx <[EMAIL PROTECTED]> wrote: >> > Package: libtasn1-3 >> > Version: 1.4-1 >> > Severity: grave >> >> > When I run "lynx https://acrobat.com", I end up with a segfault. The >> > backtrace looks like: >> [...] >> > I'm running libgnutls26 2.4.1-1 and lynx-cur 2.8.7dev9-2. >> >> FWIW I get the same behavior Simon describes ("SSL error:no issuer was >> found-Continue? (y)" followed by "Alert!: Unexpected network read >> error; connection aborted.") *both* on ix86 and amd64 (the latter on >> pergolesi.d.o's unstable_amd64 chroot), using the same versions of >> libgnutls26 and lynx-cur. >> >> Have you got any special settings in ~/lynxrc? > > No, it's the default setting. > > But it seems to be related to me using MALLOC_CHECK_=2 in the > enviroment. I thought I've set it to 0 to make sure it wasn't > related. But trying to unset or set it to 0 now stops the segfault. > > Also not that the check even with set to 3 it doesn't print any error > message.
I can't reproduce this on an x86 with MALLOC_CHECK_=2, but maybe it requires an amd64 platform. Btw, which libc6 verison do you use? I use 2.7-13. Btw, openssl's way of saying that the other end disconnected improperly appears to be to print 'read:errno=0'. This is the same as the GnuTLS error about a packet of unexpected length (i.e., packet size 0). /Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]