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

Re: 'svnadmin load' crashing reliably in Fedora Core 1

From: Garrett Rooney <rooneg_at_gmail.com>
Date: 2004-06-20 15:53:15 CEST

On Sun, 20 Jun 2004 02:13:17 -0400, Alexander L. Belikoff
<abel@vallinor4.com> wrote:
>
> Hello everyone,
>
> I've been trying to build Subversion 1.0.0 and upwards in Fedora Core 1 and I
> keep getting run-time crashes using every snapshot I try.
>
> The test is the as follows:
>
> rm -rf /tmp/repotest/ ; svnadmin create /tmp/repotest && \
> echo repository created && svnadmin load /tmp/repotest < /dev/null
>
> Svnadmin segfaults during the load operation in the following context:
>
> =======================================================
> [Thread debugging using libthread_db enabled]
> [New Thread -1085164896 (LWP 8339)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1085164896 (LWP 8339)]
> apr_palloc (pool=0x14841b, size=1344539) at apr_pools.c:608
> 608 if (size < (apr_size_t)(active->endp - active->first_avail)) {
> (gdb) p active
> $1 = (apr_memnode_t *) 0x6556000a
> (gdb) p *active
> Cannot access memory at address 0x6556000a
> (gdb)
> ========================================================

First off, why are you trying to pass svnadmin load /dev/null?
Usually one would feed svnadmin load the contents of a dumpfile...

Second, I can't reproduce this crash with a version of svnadmin built
from the trunk, so it's possible that we've already fixed it. Could
you send a backtrace from gdb so we can see what it's trying to do
when it crashes?

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 20 15:53:57 2004

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.