Re: [Ocaml-lib-devel] segfault in GC when creating a DynArray of size zero

[Janne H. <ja...@hy...>]

skaller wrote:
> Nope -- someone else reported this problem, I just
> coded it into a test.

Oh OK.  Well thanks to the original reporter then :)

I was not aware of this, so I've been thinking it's a new bug.

> Hmm. If we had unit test level control in the test
> harness, we could add/not add Gc.major() after every
> test.

Yep that's right.  We could have it as a flag for Util.run_test. 
However, this can also be done in a regression tester fashion by 
isolating the test into a new test module (new file) and then adding the 
Gc.major () call by hand.  I think this approach is perfectly reasonable 
since GC bugs should not be that frequent.

There is also a possibility (because we have your mktest) to compile a 
fresh new executable out of each test.  This way each test would be run 
in a separate process and thus they would not interfere with each other.

There are also other variations such as randomizing the order of test 
execution inside a single process etc etc.

>>$ ./mktest --author=jh --module=DynArray
>>$ ./extlib_test
> 
> Ah, you added --module :)

Yes!

$ ./mktest --author=js --author=jh --module=DynArray --module=ExtString

calculates an intersection of all modules DynArray and ExtString that 
have js or jh as the author.

I did not add --test=foo, since there's not much need for it yet.

ciao,
janne