A user has reported an error in which we have a expression like so:

{ ../../foo[../bar] }

In this case, DPath is able to successfully traverse the ../../foo expression, setting currentNode to foo. But when it tries to execute the ../bar subexpression, it uses the current node as it's context. The ../bar subexpression should be executed with the original context, but is instead executed with a currentNode of foo, which causes a failure.