|
[Rivet] segmentation fault with pythia8Lars Sonnenschein sonne at mail.cern.chTue Jul 8 10:01:37 BST 2008
I'm afraid I don't get that far with the head version. For some reason my specified AGILE_GEN_PATH variable gets ignored and from the LCG generators I get error messages like: [lxbuild021] ~/scratch0/cedar/AgileCommit > rivetgun -g Pythia6:413 -a CDF_2007_S7057202 --beam1 PROTON --beam2 ANTIPROTON --mom1 980. --mom2 980. -P ../rivetgun_params/fpythia-TuneApthatmin30.params RivetGun.Main: INFO Requested generator = Pythia6:413 rivetgun: symbol lookup error: /afs/cern.ch/sw/lcg/external/MCGenerators/pythia6/413/slc4_ia32_gcc34/lib/libpythia6.so: undefined symbol: s_cmp (Same for Herwig. Pythia8 does not show up as available, but that's because I configured with my private Pythia8 installation, I assume) Lars On Mon, 7 Jul 2008, Andy Buckley wrote: > Holger Schulz wrote: > > > 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: > > > #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 () > > Looks to me like a memory corruption, but I'm not sure how: there isn't > even a pointer in that class that could get corrupted, nor an explicit > "delete" call! > > > Has anyone observed something similar, or is my installation broken? > > I haven't tried yet ... Lars, do you see this? Any suggestions? > > > 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. > > I'm assuming that this is a legacy of ":" being a valid param definition > character. I'll look into it. Again, Lars, had you noticed this being a > problem? > > Andy > > -- ________________________________ Lars Sonnenschein ________________________________ Home Institution: PH/TH 53/1-052 CERN CH-1211 Geneve 23 Switzerland Tel.:+41(22)767-2801 -------------------------------- ________________________________ FNAL: D0, PK151 Mailstop #352 Fermilab, P.O.Box 500 Batavia, IL 60510-500 USA Tel.: +1(630)840-8740 ________________________________
More information about the Rivet mailing list |