[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SIGSEGV crash in svn export with 1.2 under Debian

From: Loïc Minier <lool+tigris_at_via.ecp.fr>
Date: 2005-07-05 19:19:29 CEST

        Hi,

On Tue, Jul 05, 2005, Philip Martin wrote:
> There's another report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316227

 Ok, I just told jb to merge our bugs if his bt matches mine, but he
 couldn't decide yet.

> The reports claim it's reproducible, so if someone could a recipe that
> would help. Providing "svn status" output for the working copy in
> question might be enough.

 It's reproducible for certain local copies, but not all...

 I couldn't reproduce the problem in 15 minutes of trying, then I went
 to another local copy, and got it...

 When I get it, I get it 100% of the time.

 svn status shows nothing, as the local copy is unmodified, for jb and
 for me.

 jb gets the bug every time after a vendor merge, I think I get it after
 commits.

 jb noted that "svn up" makes the crash vanish, and I verified that on a
 broken tree.

 I attach a diff between a "svn up"ed tree (libgnomeui.bak), not
 crashing anymore, and the tree still crashing (libgnomeui).

   Bye,

-- 
Loïc Minier <lool@dooz.org>
"Neutral President: I have no strong feelings one way or the other."


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Tue Jul 5 23:19:42 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.