You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Bernd Walter <ti...@cicely5.cicely.de> on 2002/08/10 11:44:21 UTC
How do force commits and svn --version crashing
Makefile is an unmodified file
[194]cicely5> svn commit Makefile
[195]cicely5> svn commit --force Makefile
[196]cicely5> touch Makefile
[197]cicely5> svn commit Makefile
[198]cicely5> svn commit --force Makefile
[199]cicely5> svn --version
Segmentation fault (core dumped)
Exit 139
- huch different story (this is r2927 on FreeBSD-current i386 from march)
This also happens on FreeBSD4.6-stable alpha:
[540]srv1.cosmo-project.de> svn --version
Segmentation fault (core dumped)
Exit 139
And on FreeBSD-current (27 Jul) alpha:
[62]cicely9> svn --version
Segmentation fault
Exit 139
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How do force commits and svn --version crashing
Posted by Bernd Walter <ti...@cicely5.cicely.de>.
On Sat, Aug 10, 2002 at 03:30:34PM -0700, Justin Erenkrantz wrote:
> On Sat, Aug 10, 2002 at 08:55:34PM +0200, Bernd Walter wrote:
> > > This probably means you need an updated apr.
> >
> > On the 2 machines where I also run mod_dav_svn I used the apr which
> > was embedded in Apache 2.0.39.
> > The others use the FreeBSD apr-20020707163141_1 port.
> > The intersting point is that svn --version is the only thing that
> > failed so far - svn co and so on worked fine as I can tell.
>
> Indeed, Greg was right. You need to use the updated APR. You
> can *only* use the APR version from the same date as your SVN
> checkout. No other combination is supported.
>
> In your case, your APR is out-of-date and has a bug that SVN used
> to workaround, but doesn't need to anymore since HEAD of APR is
> fixed. -- justin
Thank you - updating apr/apr-util has solved this problem.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How do force commits and svn --version crashing
Posted by Justin Erenkrantz <je...@apache.org>.
On Sat, Aug 10, 2002 at 08:55:34PM +0200, Bernd Walter wrote:
> > This probably means you need an updated apr.
>
> On the 2 machines where I also run mod_dav_svn I used the apr which
> was embedded in Apache 2.0.39.
> The others use the FreeBSD apr-20020707163141_1 port.
> The intersting point is that svn --version is the only thing that
> failed so far - svn co and so on worked fine as I can tell.
Indeed, Greg was right. You need to use the updated APR. You
can *only* use the APR version from the same date as your SVN
checkout. No other combination is supported.
In your case, your APR is out-of-date and has a bug that SVN used
to workaround, but doesn't need to anymore since HEAD of APR is
fixed. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How do force commits and svn --version crashing
Posted by Bernd Walter <ti...@cicely5.cicely.de>.
On Sat, Aug 10, 2002 at 02:32:33PM -0400, Greg Hudson wrote:
> On Sat, 2002-08-10 at 07:44, Bernd Walter wrote:
> > [198]cicely5> svn commit --force Makefile
>
> Our commit --force doesn't currently work like CVS's commit --force; it
> won't cause a commit to happen when nothing has changed. Maybe that's
> wrong; I'm not sure.
At least it's on my wish list as I'm used to force commit to extent
commitlogs and the like.
> > And on FreeBSD-current (27 Jul) alpha:
> > [62]cicely9> svn --version
> > Segmentation fault
> > Exit 139
>
> This probably means you need an updated apr.
On the 2 machines where I also run mod_dav_svn I used the apr which
was embedded in Apache 2.0.39.
The others use the FreeBSD apr-20020707163141_1 port.
The intersting point is that svn --version is the only thing that
failed so far - svn co and so on worked fine as I can tell.
But yes - it failed inside an apr function:
[58]cicely30> gdb /usr/local/bin/svn svn.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
Core was generated by `svn'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/libsvn_client-1.so.0...done.
Reading symbols from /usr/local/lib/libsvn_wc-1.so.0...done.
Reading symbols from /usr/local/lib/libexpat.so.3...done.
Reading symbols from /usr/local/lib/libsvn_ra-1.so.0...done.
Reading symbols from /usr/lib/libz.so.2...done.
Reading symbols from /usr/local/lib/libsvn_ra_local-1.so.0...done.
Reading symbols from /usr/local/lib/libsvn_repos-1.so.0...done.
Reading symbols from /usr/local/lib/libsvn_fs-1.so.0...done.
Reading symbols from /usr/local/lib/libdb4.so.0...done.
Reading symbols from /usr/local/lib/libsvn_delta-1.so.0...done.
Reading symbols from /usr/local/lib/libsvn_ra_dav-1.so.0...done.
Reading symbols from /usr/local/lib/libsvn_subr-1.so.0...done.
Reading symbols from /usr/local/lib/libaprutil.so.0...done.
Reading symbols from /usr/local/lib/libapr.so.0...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libcrypt.so.2...done.
Reading symbols from /usr/local/lib/libneon.so.21...done.
Reading symbols from /usr/local/lib/libxml.so.5...done.
Reading symbols from /usr/lib/libssl.so.2...done.
Reading symbols from /usr/lib/libcrypto.so.2...done.
Reading symbols from /usr/lib/libc.so.5...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x282092fd in apr_getopt_long (os=0x805f130, opts=0x8050400, optch=0xbfbff7a4, optarg=0xbfbff7a8) at getopt.c:240
240 len = strlen(opts[i].name);
(gdb) bt
#0 0x282092fd in apr_getopt_long (os=0x805f130, opts=0x8050400, optch=0xbfbff7a4, optarg=0xbfbff7a8) at getopt.c:240
#1 0x804d2a1 in main (argc=2, argv=0xbfbff930) at subversion/clients/cmdline/main.c:1111
#2 0x804a4b1 in _start ()
(gdb) print i
$1 = -1
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: How do force commits and svn --version crashing
Posted by Greg Hudson <gh...@MIT.EDU>.
On Sat, 2002-08-10 at 07:44, Bernd Walter wrote:
> [198]cicely5> svn commit --force Makefile
Our commit --force doesn't currently work like CVS's commit --force; it
won't cause a commit to happen when nothing has changed. Maybe that's
wrong; I'm not sure.
> And on FreeBSD-current (27 Jul) alpha:
> [62]cicely9> svn --version
> Segmentation fault
> Exit 139
This probably means you need an updated apr.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org