You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by SmartServ Hosting <je...@smart-serv.net> on 2005/01/22 02:39:00 UTC
Core dump checking out large repositories
%uname -rs
FreeBSD 5.3-RELEASE
%du -sh /svnroot
7.5M /svnroot/
Subversion: 1.1.1
%svn co file:///svnroot/trunk
[some files checkout/not all files]
Segmentation fault (core dumped)
%
backtrace:
(gdb) bt full
#0 0x280d97f3 in update_entry (b=Cannot access memory at address 0xbfad1d98
) at subversion/libsvn_repos/reporter.c:589
s_root = (svn_fs_root_t *) Cannot access memory at address 0xbfad1ddc
--
Jeremy Johnston (President / Developer)
SmartServ Hosting
Email: jeremy@smart-serv.net
Phone: 1-250-402-6634
Cell: 1-250-402-9583 | 2504029583@msg.telus.com (150 Characters max)
Fax: 1-250-402-6634
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by SmartServ Hosting <je...@smart-serv.net>.
On Sat, 22 Jan 2005 11:20:56 -0600
Ben Collins-Sussman <su...@collab.net> wrote:
>
> On Jan 22, 2005, at 10:15 AM, Dominic Mitchell wrote:
>
> > On Fri, Jan 21, 2005 at 07:39:00PM -0700, SmartServ Hosting wrote:
> >> %uname -rs
> >> FreeBSD 5.3-RELEASE
> >> %du -sh /svnroot
> >> 7.5M /svnroot/
> >>
> >> Subversion: 1.1.1
> >>
> >> %svn co file:///svnroot/trunk
> >> [some files checkout/not all files]
> >> Segmentation fault (core dumped)
> >> %
> >>
> >> backtrace:
> >> (gdb) bt full
> >> #0 0x280d97f3 in update_entry (b=Cannot access memory at address
> >> 0xbfad1d98
> >> ) at subversion/libsvn_repos/reporter.c:589
> >> s_root = (svn_fs_root_t *) Cannot access memory at address
> >> 0xbfad1ddc
> >
> > This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
> > Although I'm accessing over webdav. Now that I try it using a file:///
> > url, it goes wrong too. Which is odd, because when I tried it, it
> > didn't fail...
>
> Here's a question: is there any chance the the freebsd port is using
> APR 1.0, rather than 0.9.5?
>
> Either of those versions of APR will work with Subversion, though
> Subversion technically only claims to use 0.9.5. But the problem is
> that the two versions of APR are binary-incompatible. I've seen a lot
> of strange svn bugs lately, and many of them happen when somebody was
> using Subversion with APR 0.9.5, then quietly (or unintentionally)
> upgrades to APR 1.0.
>
> In other words, it's safe to *start* using Subversion for the first
> time with either APR 0.9.5 or 1.0. But it's not safe to switch horses
> mid-stream.
> (
>
Subersion was compiled with APR 1.0 before any repositories were created.
--
Jeremy Johnston (President / Developer)
SmartServ Hosting
Email: jeremy@smart-serv.net
Phone: 1-250-402-6634
Cell: 1-250-402-9583 | 2504029583@msg.telus.com (150 Characters max)
Fax: 1-250-402-6634
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Eric Ross <er...@disc.ucn.cl>.
On Sat, 22 Jan 2005, Dominic Mitchell wrote:
> On Sat, Jan 22, 2005 at 06:43:34PM +0000, Dominic Mitchell wrote:
>> What's disconcerting is that when I compiled the port with the
>> WITH_MAINTAINER_DEBUG option[1], the problem goes away. I'll try
>> recompiling with just "-g" in CFLAGS, so at least I can get some useful
>> info out of gdb...
>
> Unfortunately, compiling with -g also covers up the problem. This
> really is most odd.
Maybe compiling with -lefence ? (ElectricFence, or similar) ?
--
#79989 counter.li.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Dominic Mitchell <do...@happygiraffe.net>.
On Sat, Jan 22, 2005 at 06:43:34PM +0000, Dominic Mitchell wrote:
> What's disconcerting is that when I compiled the port with the
> WITH_MAINTAINER_DEBUG option[1], the problem goes away. I'll try
> recompiling with just "-g" in CFLAGS, so at least I can get some useful
> info out of gdb...
Unfortunately, compiling with -g also covers up the problem. This
really is most odd.
-Dom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Dominic Mitchell <do...@happygiraffe.net>.
On Sat, Jan 22, 2005 at 12:12:44PM -0600, Ben Collins-Sussman wrote:
> >Actually, I've just read this closer. It's about /switching/ from 0.95
> >to 1.0. In that case, would it help to recreate the repository from a
> >dump file using my currently installed version? Surely that should
> >sort
> >things out. Or are there libapr dependencies in the dumpfile?
>
> Nope, the whole point of the dumpfile is that the data is timeless and
> portable, so you can switch between versions of svn, fs backends, db
> schemas, etc. Give it a shot, see what happens.
Ok.
% ldd =svnadmin | grep apr
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x280f6000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28326000)
% svnadmin create /tmp/testrepos
% zcat /local/backup/svn/svndump-private-2005-01-22.gz | svnadmin load /tmp/testrepos
...
------- Committed revision 495 >>>
% svn co file:///tmp/testrepos/trunk
...
A trunk/etc/cricketconf/cricket-config/systemperf/ppe
zsh: segmentation fault (core dumped) svn co file:///tmp/testrepos/trunk
So sadly, it still breaks even on a brand new repository. Retrying with
an fsfs repository instead of a bdb one produces exactly the same
results.
What's disconcerting is that when I compiled the port with the
WITH_MAINTAINER_DEBUG option[1], the problem goes away. I'll try
recompiling with just "-g" in CFLAGS, so at least I can get some useful
info out of gdb...
Thanks,
-Dom
[1] Enables --enable-maintainer-mode and --enable-maintainer-mode and
puts "-g" into CFLAGS.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Ben Collins-Sussman <su...@collab.net>.
> Actually, I've just read this closer. It's about /switching/ from 0.95
> to 1.0. In that case, would it help to recreate the repository from a
> dump file using my currently installed version? Surely that should
> sort
> things out. Or are there libapr dependencies in the dumpfile?
>
Nope, the whole point of the dumpfile is that the data is timeless and
portable, so you can switch between versions of svn, fs backends, db
schemas, etc. Give it a shot, see what happens.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Dominic Mitchell <do...@happygiraffe.net>.
On Sat, Jan 22, 2005 at 10:50:36AM -0700, SmartServ Hosting wrote:
> On Sat, 22 Jan 2005 17:43:21 +0000
> dom@happygiraffe.net (Dominic Mitchell) wrote:
>
> > On Sat, Jan 22, 2005 at 11:20:56AM -0600, Ben Collins-Sussman wrote:
> > > On Jan 22, 2005, at 10:15 AM, Dominic Mitchell wrote:
> > > >This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
> > > >Although I'm accessing over webdav. Now that I try it using a file:///
> > > >url, it goes wrong too. Which is odd, because when I tried it, it
> > > >didn't fail...
> > >
> > > Here's a question: is there any chance the the freebsd port is using
> > > APR 1.0, rather than 0.9.5?
> > >
> > > Either of those versions of APR will work with Subversion, though
> > > Subversion technically only claims to use 0.9.5. But the problem is
> > > that the two versions of APR are binary-incompatible. I've seen a lot
> > > of strange svn bugs lately, and many of them happen when somebody was
> > > using Subversion with APR 0.9.5, then quietly (or unintentionally)
> > > upgrades to APR 1.0.
> > >
> > > In other words, it's safe to *start* using Subversion for the first
> > > time with either APR 0.9.5 or 1.0. But it's not safe to switch horses
> > > mid-stream.
> >
> > In my case:
> >
> > % ldd /usr/local/bin/svn| grep apr
> > libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x2817b000)
> > libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28389000)
> >
> > According to the ports Makefile[1], if you select the WITH_MOD_DAV_SVN
> > option (as I have done), you get the APR that comes with apache (2.0.52
> > in my case).
> >
> > Unfortunately, I've just attempted a debug build of subversion and that
> > works without error, which is most irritating.
> >
> > -Dom
> >
> > [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/Makefile
>
> %ldd /usr/local/bin/svn | grep apr
> libaprutil-1.so.0 => /usr/local/lib/libaprutil-1.so.0 (0x28147000)
> libapr-1.so.0 => /usr/local/lib/libapr-1.so.0 (0x28327000)
Actually, I've just read this closer. It's about /switching/ from 0.95
to 1.0. In that case, would it help to recreate the repository from a
dump file using my currently installed version? Surely that should sort
things out. Or are there libapr dependencies in the dumpfile?
-Dom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by SmartServ Hosting <je...@smart-serv.net>.
On Sat, 22 Jan 2005 17:43:21 +0000
dom@happygiraffe.net (Dominic Mitchell) wrote:
> On Sat, Jan 22, 2005 at 11:20:56AM -0600, Ben Collins-Sussman wrote:
> > On Jan 22, 2005, at 10:15 AM, Dominic Mitchell wrote:
> > >This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
> > >Although I'm accessing over webdav. Now that I try it using a file:///
> > >url, it goes wrong too. Which is odd, because when I tried it, it
> > >didn't fail...
> >
> > Here's a question: is there any chance the the freebsd port is using
> > APR 1.0, rather than 0.9.5?
> >
> > Either of those versions of APR will work with Subversion, though
> > Subversion technically only claims to use 0.9.5. But the problem is
> > that the two versions of APR are binary-incompatible. I've seen a lot
> > of strange svn bugs lately, and many of them happen when somebody was
> > using Subversion with APR 0.9.5, then quietly (or unintentionally)
> > upgrades to APR 1.0.
> >
> > In other words, it's safe to *start* using Subversion for the first
> > time with either APR 0.9.5 or 1.0. But it's not safe to switch horses
> > mid-stream.
>
> In my case:
>
> % ldd /usr/local/bin/svn| grep apr
> libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x2817b000)
> libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28389000)
>
> According to the ports Makefile[1], if you select the WITH_MOD_DAV_SVN
> option (as I have done), you get the APR that comes with apache (2.0.52
> in my case).
>
> Unfortunately, I've just attempted a debug build of subversion and that
> works without error, which is most irritating.
>
> -Dom
>
> [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/Makefile
%ldd /usr/local/bin/svn | grep apr
libaprutil-1.so.0 => /usr/local/lib/libaprutil-1.so.0 (0x28147000)
libapr-1.so.0 => /usr/local/lib/libapr-1.so.0 (0x28327000)
--
Jeremy Johnston (President / Developer)
SmartServ Hosting
Email: jeremy@smart-serv.net
Phone: 1-250-402-6634
Cell: 1-250-402-9583 | 2504029583@msg.telus.com (150 Characters max)
Fax: 1-250-402-6634
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Dominic Mitchell <do...@happygiraffe.net>.
On Sat, Jan 22, 2005 at 11:20:56AM -0600, Ben Collins-Sussman wrote:
> On Jan 22, 2005, at 10:15 AM, Dominic Mitchell wrote:
> >This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
> >Although I'm accessing over webdav. Now that I try it using a file:///
> >url, it goes wrong too. Which is odd, because when I tried it, it
> >didn't fail...
>
> Here's a question: is there any chance the the freebsd port is using
> APR 1.0, rather than 0.9.5?
>
> Either of those versions of APR will work with Subversion, though
> Subversion technically only claims to use 0.9.5. But the problem is
> that the two versions of APR are binary-incompatible. I've seen a lot
> of strange svn bugs lately, and many of them happen when somebody was
> using Subversion with APR 0.9.5, then quietly (or unintentionally)
> upgrades to APR 1.0.
>
> In other words, it's safe to *start* using Subversion for the first
> time with either APR 0.9.5 or 1.0. But it's not safe to switch horses
> mid-stream.
In my case:
% ldd /usr/local/bin/svn| grep apr
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x2817b000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28389000)
According to the ports Makefile[1], if you select the WITH_MOD_DAV_SVN
option (as I have done), you get the APR that comes with apache (2.0.52
in my case).
Unfortunately, I've just attempted a debug build of subversion and that
works without error, which is most irritating.
-Dom
[1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/subversion/Makefile
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jan 22, 2005, at 10:15 AM, Dominic Mitchell wrote:
> On Fri, Jan 21, 2005 at 07:39:00PM -0700, SmartServ Hosting wrote:
>> %uname -rs
>> FreeBSD 5.3-RELEASE
>> %du -sh /svnroot
>> 7.5M /svnroot/
>>
>> Subversion: 1.1.1
>>
>> %svn co file:///svnroot/trunk
>> [some files checkout/not all files]
>> Segmentation fault (core dumped)
>> %
>>
>> backtrace:
>> (gdb) bt full
>> #0 0x280d97f3 in update_entry (b=Cannot access memory at address
>> 0xbfad1d98
>> ) at subversion/libsvn_repos/reporter.c:589
>> s_root = (svn_fs_root_t *) Cannot access memory at address
>> 0xbfad1ddc
>
> This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
> Although I'm accessing over webdav. Now that I try it using a file:///
> url, it goes wrong too. Which is odd, because when I tried it, it
> didn't fail...
Here's a question: is there any chance the the freebsd port is using
APR 1.0, rather than 0.9.5?
Either of those versions of APR will work with Subversion, though
Subversion technically only claims to use 0.9.5. But the problem is
that the two versions of APR are binary-incompatible. I've seen a lot
of strange svn bugs lately, and many of them happen when somebody was
using Subversion with APR 0.9.5, then quietly (or unintentionally)
upgrades to APR 1.0.
In other words, it's safe to *start* using Subversion for the first
time with either APR 0.9.5 or 1.0. But it's not safe to switch horses
mid-stream.
(
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Core dump checking out large repositories
Posted by Dominic Mitchell <do...@happygiraffe.net>.
On Fri, Jan 21, 2005 at 07:39:00PM -0700, SmartServ Hosting wrote:
> %uname -rs
> FreeBSD 5.3-RELEASE
> %du -sh /svnroot
> 7.5M /svnroot/
>
> Subversion: 1.1.1
>
> %svn co file:///svnroot/trunk
> [some files checkout/not all files]
> Segmentation fault (core dumped)
> %
>
> backtrace:
> (gdb) bt full
> #0 0x280d97f3 in update_entry (b=Cannot access memory at address 0xbfad1d98
> ) at subversion/libsvn_repos/reporter.c:589
> s_root = (svn_fs_root_t *) Cannot access memory at address 0xbfad1ddc
This is exactly the same problem that I am seeing, on FreeBSD-CURRENT.
Although I'm accessing over webdav. Now that I try it using a file:///
url, it goes wrong too. Which is odd, because when I tried it, it
didn't fail...
At least this should make the debugging easier, without apache
involved.
-Dom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org