[Rivet] segmentation fault with pythia8

[Holger Schulz]

Hi,

I played around a bit with pythia8 (version .107 and .108) and rivet 
(latest svn version) and I found something odd.

If one, for example, calls
            rivetgun -g Pythia8:108 -n 1000 -P lep1.params
there is a normal exit. (except that nothing happens since no process is 
switched on)

But if I switch on a process like
            rivetgun -g Pythia8:108 -n 1000 -P lep1.params -p 
"WeakSingleBoson:ffbar2gmZ=on"
there is a segmentation fault at the end after finalize() is called.

here is some gdb output:
        Program received signal SIGSEGV, Segmentation fault.
        [Switching to Thread -1344788784 (LWP 15115)]
        0x43f2c9e9 in __gnu_cxx::__exchange_and_add () from 
/usr/lib/libstdc++.so.6
        (gdb) bt
        #0  0x43f2c9e9 in __gnu_cxx::__exchange_and_add () from 
/usr/lib/libstdc++.so.6
        #1  0x9d21165b in AGILe::CCPythia::~CCPythia$delete () from 
/mnt/eeh/hschulz/Software/lib/libAGILeCCPythia.so
        #2  0xafee85aa in AGILe::Loader::destroyGen () from 
/users/eeh/hschulz/Software/lib/libAGILe.so.0
        #3  0x08053dba in Rivet::generate ()
        #4  0x080500ef in main ()



Has anyone observed something similar, or is my installation  broken?

Furthermore, it seems as if prof-tune doesn't handle statements like -p 
"WeakSingleBoson:ffbar2gmZ=on"
properly, since the output in out.log then gives lines as such:

             PYTHIA Abort from Pythia::next: not properly initialized so 
cannot generate events             
             Event generation aborted prematurely
Reading these parameter settings from a file with -P doesn't work 
either. On the other hand,
the parameter values that shall be varied are handed over correctly.

Holger