On 4/10/2015 9:07 AM, Dewayne Geraghty wrote:
>
>
> On 10/04/2015 11:47 AM, Aristedes Maniatis wrote:
>> Dewayne Geraghty wrote:
>>> Most likely there was a port build that required openssl port, and also
>>> required
>>> something like libarchive or libfetch (for example), both require openssl
On Thu, Apr 09, 2015 at 05:52:48PM +0300, Kimmo Paasiala wrote:
> On Thu, Apr 9, 2015 at 3:43 PM, Dewayne Geraghty
> wrote:
> >
> > On 9/04/2015 10:02 PM, Kimmo Paasiala wrote:
> >> On Thu, Apr 9, 2015 at 1:42 PM, Aristedes Maniatis wrote:
> >>> Starting in the last week or so, several different
On Thu, Apr 9, 2015 at 3:43 PM, Dewayne Geraghty
wrote:
>
> On 9/04/2015 10:02 PM, Kimmo Paasiala wrote:
>> On Thu, Apr 9, 2015 at 1:42 PM, Aristedes Maniatis wrote:
>>> Starting in the last week or so, several different applications are
>>> exhibiting the same symptoms of broken libcrypto libra
On 9/04/2015 10:02 PM, Kimmo Paasiala wrote:
> On Thu, Apr 9, 2015 at 1:42 PM, Aristedes Maniatis wrote:
>> Starting in the last week or so, several different applications are
>> exhibiting the same symptoms of broken libcrypto libraries.
>>
>> (gdb) core bash.core
>> Core was generated by `bash
On Thu, Apr 9, 2015 at 1:42 PM, Aristedes Maniatis wrote:
> Starting in the last week or so, several different applications are
> exhibiting the same symptoms of broken libcrypto libraries.
>
> (gdb) core bash.core
> Core was generated by `bash'.
> Program terminated with signal 11, Segmentation
Starting in the last week or so, several different applications are exhibiting
the same symptoms of broken libcrypto libraries.
(gdb) core bash.core
Core was generated by `bash'.
Program terminated with signal 11, Segmentation fault.
(gdb) bt
#0 0x0008029cafe5 in OPENSSL_ia32_cpuid () from
