On Tue, May 27, 2014 at 04:10:39PM -0700, Jason Evans wrote: > > As for running tests, the following unit tests crash: > > - ckh > > - rtree > > - tsd > > > > They all crash in malloc_tsd_malloc, which is fishy. > > Probably a bootstrapping order issue, but I don't have any concrete guesses > as to how it's failing.
And it is. It is caused by those tests assuming that jemalloc is initialized as a side effect of the constructor added in 20f1fc95adb35ea63dc61f47f2b0ffbd37d39f32, which doesn't run on msvc builds, and is not needed since there is no fork(). Do you think it's better to make jemalloc initialize itself on msvc builds anyways, or to make those tests explicitely initialize jemalloc? With that fixed, as well as the ssize_t thing, that leaves me with: - SFMT crashing in gen_rand_array - thread_arena assertions - math.c and mq.c failure to build Mike _______________________________________________ jemalloc-discuss mailing list jemalloc-discuss@canonware.com http://www.canonware.com/mailman/listinfo/jemalloc-discuss
