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

Re: put_xlate_handle_node exception

From: Kevin Radke <kmradke_at_gmail.com>
Date: Wed, 15 Apr 2015 08:19:56 -0500

Philip,

I'm using --disable-nonportable-atomics and apr 1.5.1 compiled with gcc
4.4.7.
httpd 2.2.29 is built with mpm=worker.

make check in svn gives:
Summary of test results:
  1948 tests PASSED
  58 tests SKIPPED
  31 tests XFAILED (1 WORK-IN-PROGRESS)
SUMMARY: All tests successful.

Kevin R,

On Wed, Apr 15, 2015 at 4:25 AM, Philip Martin <philip.martin_at_wandisco.com>
wrote:

> Kevin Radke <kmradke_at_gmail.com> writes:
>
> > I recently built svn 1.8.13 on a x64 Linux machine with self-built
> > dependencies that are current for Apache 2.2.29 (mpm=worker). I'm seeing
> > the following exception periodically and I'm looking for help to try and
> > figure out the cause.
> >
> >
> > httpd: subversion/libsvn_subr/utf.c:426: put_xlate_handle_node: Assertion
> > `node->next == ((void *)0)' failed.
> > [Tue Apr 14 16:12:40 2015] [notice] child pid 14683 exit signal Aborted
> (6)
> >
> >
> > Any pointers on what the assert is trying to protect against would be
> > helpful.
>
> The node pointer passed to put_xlate_handle_node() is obtained by
> calling get_xlate_handle_node() and all nodes returned by that function
> are expected to have node->next==NULL. If the assert fails it may
> indicate a threading problem, somehow a node is being used by multiple
> threads simultaneously. Which APR are you using? Is it build with
> portable or nonportable atomics? There was a bug in APR atomic
> operations in the past, perhaps you are seeing a variant of
> http://subversion.apache.org/docs/release-notes/1.7.html#rhel-2-issue
>
> --
> Philip Martin | Subversion Committer
> WANdisco // *Non-Stop Data*
>
Received on 2015-04-15 15:20:36 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.