Am 27.03.2010 00:15, schrieb David Rothenberger: > On 3/26/2010 2:07 PM, Corinna Vinschen wrote: >> On Mar 26 11:12, David Rothenberger wrote: >>> On 3/26/2010 2:32 AM, Corinna Vinschen wrote: >>>> On Mar 26 15:40, Nayuta Taga wrote: >>>>> "svn --version" hals in 1.7.2-2 on both Windows7 and XP. >>> [snip] >>>> >>>> Works for me. BLODA? >>> >>> I'm able to reproduce this on one of my three Windows XP machines. >>> Ironically, the only one without a Symantec product installed. >>> >>> On 3/26/2010 4:23 AM, Dave Korn wrote: >>>> I had mysterious problems with svn once which didn't go away until I got >>>> rid >>>> of all the sasl2 stuff from my installation, so this theory is worth >>>> pursuing. >>> >>> I recompiled without sasl2 support directly in svn and that fixed the >>> problem for me. This didn't require disabling serf, by the way. >>> >>> I'm not sure why this is hanging on some machines and not others. I see >>> in Process Explorer there's a UDP connection related to sasl2 open when >>> the process is hanging, but I haven't had time to investigate further. >> >> There's an open UDP connection when calling `svn --version'??? > > Yup. Here's the thread stack at the time the connection was created: > > !connect+0x53 > !cygwin_internal+0x2b0d5 > !setlogmask+0xce8 > !setlogmask+0xdff > !aclcheck+0x11836 > !sasl_log+0x123 > !sasl_get_plugin+0xa6 > !sasl_load_plugins+0x2e3 > !sasl_client_init+0xdf > !svn_ra_svn__sasl_init+0x9c > !svn_atomic__init_once+0x49 > !svn_ra_svn__sasl_init+0x22 > !svn_ra_print_modules+0x5d > > The sasl_log thing caused me to check /var/log/messages. Here's what > I found: > > Mar 26 15:53:28 localhost unable: to dlopen > /usr/lib/sasl2/cygdigestmd5-2.dll: No such file or directory > Mar 26 15:53:28 localhost unable: to dlopen /usr/lib/sasl2/cygotp-2.dll: No > such file or directory > > Which is weird, because those DLLs are there. So, next I tried an > strace. I noticed that the /usr/lib/sasl2/*.la files were being > opened, which also seemed weird. > > So I tried uninstalling libsasl2-devel. It worked! No hang! This > seems to be the key. The sasl2 initialization appears to hang if the > -devel package is installed, otherwise it works fine. > >> I just tested on an up-to-date XP SP3 machine and it also works fine >> there, no hangs. > > Works fine for me on all machines without libsasl2-devel. BTW, it > appears Matthias also had the -devel package installed, because his > strace also shows attempts to open the .la files in /usr/lib/sasl2. >
Indeed I used to have libsasl2-devel installed. For me, too, removing libsasl2-devel has fixed the hang. -- Matthias Andree -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
