[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libssh 0.8.1 breaks amarok
[Thread Prev] | [Thread Next]
- Subject: Re: libssh 0.8.1 breaks amarok
- From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Wed, 22 Aug 2018 09:51:12 +0200
- To: libssh@xxxxxxxxxx
On Tue, Aug 21, 2018 at 4:50 PM, Anderson Sasaki <ansasaki@xxxxxxxxxx> wrote: > ----- Original Message ----- >> From: "Antonio Rojas" <arojas@xxxxxxxxxxxxx> >> To: libssh@xxxxxxxxxx >> Sent: Tuesday, August 21, 2018 4:08:43 PM >> Subject: Re: libssh 0.8.1 breaks amarok >> >> El martes, 21 de agosto de 2018 15:26:13 (CEST) Andreas Schneider escribió: >> > > Breakpoint 1, _ssh_init (constructor=constructor@entry=1) at >> > > /usr/src/debug/libssh-0.8.1/src/init.c:63 (gdb) bt >> > > #0 _ssh_init (constructor=constructor@entry=1) at >> > >> > Can you step through this function so that we see what it is actually >> > doing? [...] > Thank you for this. Following the traces, it seems everything went fine in the libssh initialization. > > But it seems this lead to an error when initializing the threads in mariadb. As the comment in [1] point out, the library initialization can fail only because of issues when initializing threads or due to out of memory. > > I'll have to debug this further, but it is intriguing for me why this happens only when using OpenSSL. A difference of openssl (1.1) with the other back-ends is that openssl is linked with libpthreads explicitly. regards, Nikos
libssh 0.8.1 breaks amarok | Antonio Rojas <arojas@xxxxxxxxxxxxx> |
Re: libssh 0.8.1 breaks amarok | Antonio Rojas <arojas@xxxxxxxxxxxxx> |
Re: libssh 0.8.1 breaks amarok | Andreas Schneider <asn@xxxxxxxxxxxxxx> |
Re: libssh 0.8.1 breaks amarok | Antonio Rojas <arojas@xxxxxxxxxxxxx> |
Re: libssh 0.8.1 breaks amarok | Anderson Sasaki <ansasaki@xxxxxxxxxx> |