On Sun, Sep 16, 2012 at 08:05:20PM +0000, David Holland wrote:
> On Sun, Sep 16, 2012 at 07:55:16PM +0000, David Holland wrote:
> > No, I take it back, it's not my test environment. Nor is it libffi, it
> > turns out. It works in 6.99.7, fails in 6.99.11, both amd64. I wonder
> > if it's related to execinfo.
>
> Nope, looks to be openssl.
>
> #0 0x00007f7ff68f7d70 in strcmp () from /usr/lib/libc.so.12
> #1 0x00007f7febd40352 in ?? () from /usr/lib/libcrypto.so.7
> #2 0x00007f7febd405da in lh_insert () from /usr/lib/libcrypto.so.7
> #3 0x00007f7febd0f663 in OBJ_NAME_add () from /usr/lib/libcrypto.so.7
> #4 0x00007f7fec61e801 in SSL_library_init () from /usr/lib/libssl.so.10
> #5 0x00007f7feca058d2 in init_ssl ()
> from build/lib.netbsd-6.99.11-amd64-2.7/_ssl.so
> #6 0x00007f7ff78e1fe5 in _PyImport_LoadDynamicModule ()
> from /usr/pkgsrc/lang/python27/work/Python-2.7.3/libpython2.7.so.1.0
> :
>
> I suppose it's time to take this to current-users.
So, is anyone else seeing this, or is it something weird/broken
locally?
(And if so, does it affect -6? The new openssl was pulled up to -6 so
it might.)