Re: SIGSEGV in hypermail 2.0b2, other bug-o's

From: Daniel Stenberg <>
Date: Wed, 12 Aug 1998 00:44:53 +0200 (MET DST)
Message-ID: <>

On Tue, 11 Aug 1998, William F. Maton wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x3e61632e in ?? ()
> (gdb) bt
> #0 0x3e61632e in ?? ()
> #1 0x6f52202c in ?? ()
> Cannot access memory at address 0x61776174.

 I managed to get this bug too (with some "help" from Kent :-) and I must admit it bugged me for hours until I tracked it down to a single-byte buffer overflow in the line continuation function (which is used pretty frequently). Yes, its a suprise it works this good in spite of that! :-)

 I have sent the fix for that to Kent for inclusion in beta3.

             Daniel Stenberg -
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Received on Wed 12 Aug 1998 12:47:57 AM GMT

This archive was generated by hypermail 2.2.0 : Thu 22 Feb 2007 07:33:49 PM GMT GMT