------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1384
--- Comment #1 from Philip Hazel <ph10@???> 2013-09-11 14:48:35 ---
On Wed, 11 Sep 2013, Fred Koschara wrote:
> 1. ./configure --enable-pcre16 --enable-pcre32 --enable-jit --enable-utf
> --enable-unicode-properties --with-link-size=4 --enable-rebuild-chartables
> --enable-pcregrep-libz --enable-pcregrep-libbz2 --with-pcregrep-bufsize=65536
> 2. make
> 3. make check, RunTest segfaulted (it would be nice if test-suite.log gave more
> information!)
> 4. make distclean
> 5. repeat [1-4] with fewer ./configure options until RunTest passed:
> ./configure --enable-rebuild-chartables --enable-pcregrep-libz
> --enable-pcregrep-libbz2
> 6. ./configure --enable-jit --enable-rebuild-chartables --enable-pcregrep-libz
> --enable-pcregrep-libbz2
> 7. make
> 8. make check, RunTest segfaulted
> 9. make distclean
> 10. ./configure --enable-pcre16 --enable-pcre32 --enable-utf
> --enable-unicode-properties --with-link-size=4 --enable-rebuild-chartables
> --enable-pcregrep-libz --enable-pcregrep-libbz2 --with-pcregrep-bufsize=65536
> (same as step 1, minus "--enable-jit")
> 11. make
> 12. make check, RunTest passed
>
> Conclusion: --enable-jit causes segfaults in RunTest (but what test in
> RunTest??)
Thanks for your detailed report. Needless to say, RunTest works fine
with JIT on my box, and I presume in many other environments, because
8.33 has been out for a while and you are the first to report this.
You can find out more about what test failed by running RunTest as a
command on its own (not via "make check"). The output from the failing
test will be in a file called testtry and the stdout output on your
screen will identify which test is being run. In the testtry output, the
final few lines should identify the pattern and data that are causing
the problem. Please post any further information you can glean.
Philip
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
