On Wed, Aug 29, 2012 at 10:20 AM, Philip Martin <philip.mar...@wandisco.com>wrote:
> Stefan Fuhrmann <stefan.fuhrm...@wandisco.com> writes: > > > Could someone give me the additional information (stack trace?) > > that the JVM error messages is talking about? > > > > So far, I valgrinded the server side and nothing bad showed up. > > On Linux I get: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7ffff7fdf700 (LWP 30121)] > 0x00007fffc2182551 in svn_cache__get (value_p=0x7ffff7fdd518, > found=0x7ffff7fdd464, cache=0x0, key=0x7ffff7fdd448, > result_pool=0x7fffc4163ac8) at ../src/subversion/libsvn_subr/cache.c:79 > 79 cache->reads++; > (gdb) bt > #0 0x00007fffc2182551 in svn_cache__get (value_p=0x7ffff7fdd518, > found=0x7ffff7fdd464, cache=0x0, key=0x7ffff7fdd448, > result_pool=0x7fffc4163ac8) at ../src/subversion/libsvn_subr/cache.c:79 > Gotcha! If you dump from a txn fs_t instance, caches will not have been created. Thanks ya'll for the help! -- Stefan^2. -- * Join us this October at Subversion Live 2012<http://www.wandisco.com/svn-live-2012> for two days of best practice SVN training, networking, live demos, committer meet and greet, and more! Space is limited, so get signed up today<http://www.wandisco.com/svn-live-2012> ! *
