I'm a newbie too, but this looks like a backtrace that I saw the other
night when I was running cvs2svn.py to import my depot, and ran out of
disk in a partition (I didn't realise that I'd get hundreds of megs of
database log files!) It was certainly in the cleanup handlers like this
that I saw the problem.
Cheers,
Nick
jonatan wrote:
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 1024 (runnable)]
> 0x2ad010e1 in __kill () at __kill:-1
> -1 __kill: No such file or directory.
> in __kill
> (gdb) bt
> #0 0x2ad010e1 in __kill () at __kill:-1
> #1 0x2acd651a in raise (sig=6) at signals.c:65
> #2 0x2ad02570 in abort () at ../sysdeps/generic/abort.c:88
> #3 0x2ab9ccb8 in default_warning_func (pool=0x8099a20, baton=0x0,
> fmt=0x2aba9047 "%s") at subversion/libsvn_fs/fs.c:107
> #4 0x2ab9cf2e in cleanup_fs_apr (data=0x8099a58)
> at subversion/libsvn_fs/fs.c:237
> #5 0x2ac2a623 in run_cleanups (c=0x8099b88) at apr_pools.c:1961
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 29 12:26:09 2002