Re: segmentation fault with libcrypto.so (but not libcrypto.a)

To: N N <nothere44@gmail.com>
Cc: debian-devel@lists.debian.org
Subject: Re: segmentation fault with libcrypto.so (but not libcrypto.a)
From: Michael Banck <mbanck@debian.org>
Date: Tue, 3 Nov 2009 19:24:38 +0100
Message-id: <[🔎] 20091103182438.GR23240@nighthawk.chemicalconnection.dyndns.org>
In-reply-to: <[🔎] 7478a1340911030929u328ec945qa8074595466dcb48@mail.gmail.com>
References: <[🔎] 7478a1340911021725m3244a75er80359d5b9d682f8a@mail.gmail.com> <[🔎] 87k4y7izdy.fsf@frosties.localdomain> <[🔎] 7478a1340911030929u328ec945qa8074595466dcb48@mail.gmail.com>

Hi,

On Tue, Nov 03, 2009 at 12:29:46PM -0500, N N wrote:
> Since people didn't like the previous code, try the following version with
> safer memory handling.  

Debian-devel is not a bug-reporting or programming-discussion list.
Please post elsewhere.


thanks,

Michael

Reply to:

References:
- segmentation fault with libcrypto.so (but not libcrypto.a)
  - From: N N <nothere44@gmail.com>
- Re: segmentation fault with libcrypto.so (but not libcrypto.a)
  - From: Goswin von Brederlow <goswin-v-b@web.de>
- Re: segmentation fault with libcrypto.so (but not libcrypto.a)
  - From: N N <nothere44@gmail.com>

Prev by Date: Re: Lintian based autorejects
Next by Date: Bug#554194: ifupdown virtual package name and mass-filing (if accepted)
Previous by thread: Re: segmentation fault with libcrypto.so (but not libcrypto.a)
Next by thread: Re: segmentation fault with libcrypto.so (but not libcrypto.a)
Index(es):
- Date
- Thread