X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4BAD401C.8000504@acm.org> Date: Fri, 26 Mar 2010 16:15:40 -0700 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: "svn --version" halts in 1.7.2-2 References: <20100326093204.GS7718@calimero.vinschen.de> <4BACF903.70304@acm.org> <20100326210701.GY7718@calimero.vinschen.de> In-Reply-To: <20100326210701.GY7718@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. -- David Rothenberger ---- daveroth@acm.org Harriet's Dining Observation: In every restaurant, the hardness of the butter pats increases in direct proportion to the softness of the bread. -- 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