As I already said privately it would be helpful if you could reproduce
the fault...
People at FA who are testing 2.2.2 are warned there are problems ahead,
still if they could continue their tests and provide more feedback that
would be great
anyway, I'm sorry, it seems I'm not able to do anymore my work the way
it's supposed to be done. Perhaps I need some vacation and Rivet
probably needs fresh energies
thanks
-- Massimo
On 04/20/2015 05:25 PM, Brice Hamon wrote:
Hi Massimo,
I am getting this all the time with Rivet 2.2.2
[Sun Apr 19 14:23:02 2015] [notice] child pid 18013 exit signal
Segmentation fault (11)
[Sun Apr 19 14:23:04 2015] [notice] child pid 18010 exit signal
Segmentation fault (11)
[Sun Apr 19 14:24:39 2015] [notice] child pid 18107 exit signal
Segmentation fault (11)
[Sun Apr 19 14:24:40 2015] [notice] child pid 18080 exit signal
Segmentation fault (11)
[Sun Apr 19 14:24:41 2015] [notice] child pid 17998 exit signal
Segmentation fault (11)
[Sun Apr 19 14:26:31 2015] [notice] child pid 17916 exit signal
Segmentation fault (11)
[Sun Apr 19 14:26:32 2015] [notice] child pid 18105 exit signal
Segmentation fault (11)
[Sun Apr 19 14:26:33 2015] [notice] child pid 18145 exit signal
Segmentation fault (11)
I reverted to Rivet 2.1.3 and those crashes do not happen.
I compile plain vanilla with :
It was created by Rivet configure 2.2.2, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure --with-tcl=/usr/local/lib64
--with-tclsh=/usr/local/bin/tclsh8.6 --with-apache=/usr
--with-rivet-target-dir=/usr/lib/rivet --with-apxs=/usr/sbin/apxs2
No error all look good.
Any ideas ?
Thanks you,
B.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
