Re: another way to produce path.ml assertion failure assertion failure, tested versions 2.40.65 and 2.48.3

On Mon, Jul 20, 2015 at 11:15:18PM -0400, Julian Squires wrote:
> On Mon, Jul 20, 2015 at 10:35 PM, Frederik Eaton <[email protected]> wrote:
> > I'm wondering if this problem is due to a recent change in OCaml
> > libraries, since I don't think an obvious bug like this would have
> > persisted for 14 years? I don't know much about OCaml but it looks
> > like the 'unison' binary doesn't link any OCaml DLLs... OTOH a lot of
> > your String operations trigger deprecation warnings.
> 
> What version of OCaml are you using?  Strings are becoming immutable
> in newer releases, but code should only have warnings.  You might see
> if the problem persists compliing with 4.01.

I'm running Arch and the OCaml version is 4.02.1-1. However, the
Debian system I tested on has Objective Caml 3.12.1, Unison 2.40.65,
and they both produce assertion failures in path.ml. Are others not
able to reproduce the bug by running the scripts I provided?