lockup in socket_wrapper?

[Andreas Schneider]

On Friday, 26 January 2018 17:06:55 CET Volker Lendecke via samba-technical 
wrote:
> On Fri, Jan 26, 2018 at 04:51:19PM +0100, Volker Lendecke via samba-
technical wrote:
> > Hi!
> > 
> > Trying a
> > 
> > make test TESTS=smbclient_ntlm.plain
> > 
> > in master (d4f7d9e08ca690b8278b35690dfb9e4673c19e00) on a debian
> > stretch leads to a hung python process:
> > 
> > vlendec at vl-vm1:~/git/scratch$ ps uww 28795
> > USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
> > vlendec  28795  0.0  0.1  40892  7308 pts/25   S    16:45   0:00
> > /usr/bin/python /data/vlendec/git/scratch/selftest/tests.py
> > 
> > with this stack trace:
> > 
> > #0  __lll_lock_wait () at
> > ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 
> > 0x00007f8461af4b95 in __GI___pthread_mutex_lock (mutex=0x7f846295a148
> > <libc_symbol_binding_mutex>) at ../nptl/pthread_mutex_lock.c:80 #2 
> > 0x00007f84627504d9 in swrap_thread_prepare () at
> > ../third_party/socket_wrapper/socket_wrapper.c:5909
> Hmm. This happens if you have socket_wrapper already in the LD_PRELOAD
> variable. Confusing...

What do you mean with you have that already in the LD_PRELOAD variable?



-- 
Andreas Schneider                   GPG-ID: CC014E3D
Samba Team                             asn at samba.org
www.samba.org