GSI Forum - RDF feed
type: channel
description: GSI Helmholtzzentrum für Schwerionenforschung
items: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
items: Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault

Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: During the computing week in Torino I encountered a problem with running macros. We should run the macros in 'macro/pid', but unfortunately I wasn't able to do so. Running the macros 'run_sim_sttcombi_pgun.C' and 'run_digi_sttcombi.C' went through just fine, but with 'run_reco_sttcombi.C' a segmentation violation crashed the program: Quote: -I- PndMCTrackAssociator::Init [INFO ] Branch: STTHitMix not found in Tree [INFO ] Branch: STTHitMix not found in Tree -W- PndMCTrackAssociator::Init: Using STTHit array [INFO ] Branch: MVDHitsStripMix not found in Tree [INFO ] Branch: MVDHitsStripMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsStrip array [INFO ] Branch: MVDHitsPixelMix not found in Tree [INFO ] Branch: MVDHitsPixelMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsPixel [INFO ] The number of entries in chain is 10 Found Tracks: 21 in event no. 0 ---------------- Track 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 Track 1 EntryNr: 0 EntryNr: 0 EntryNr: 0 [same for tracks 2-19] Track 20 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 *** Break *** segmentation violation =========================================================== There was a crash. This is the entire stack trace of all threads: =========================================================== Thread 1 (process 34695): #0 0x00007fff82fc1168 in wait4 () #1 0x00007fff8c4255f5 in system () #2 0x00000001000d6ca8 in TUnixSystem::StackTrace () #3 0x00000001000d4ada in TUnixSystem::DispatchSignals () #4 <signal handler called> #5 PndSttMvdTracking::EliminateSpuriousSZ (this=0x109e00000, nPixelHitsinTrack=0x400735e5736ac382, ListPixelHitsinTrack=0x402211df773b3962, nStripHitsinTrack=0x109e00d4a, ListStripHitsinTrack=0x109e06cd4, nSkewHitsinTrack=0x109e00a2a, ListSkewHitsinTrack=0x4021880a31394ea5, S=0x7fff5fba0308, ZED=0x7fff5fb9fc68, DriftRadius=0x7fff5fb9f5c8, ErrorDriftRadius=0x7fff5fb9ef28, SchosenPixel=0x7fff5fadc9c8, SchosenStrip=0x7fff5fa194c8, SchosenSkew=0x7fff5…
creator: André Zambanini
date: 2012-07-24T12:05:15-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: hello Andre', it looks like you are requesting a simulation with the pileup included [namely the addition of extra hits in the STT and Mvd system caused by previous/subsequent events] but I imagine that you did not set the filename in your macro where the previously generated pileup events should exist. If my hypothesis is right then either you disable the pileup event machinery or you provide the files. To be certain, first of all please show me the exact Macro you are using, thanks Gianluigi André Goerres wrote on Tue, 24 July 2012 14:05 During the computing week in Torino I encountered a problem with running macros. We should run the macros in 'macro/pid', but unfortunately I wasn't able to do so. Running the macros 'run_sim_sttcombi_pgun.C' and 'run_digi_sttcombi.C' went through just fine, but with 'run_reco_sttcombi.C' a segmentation violation crashed the program: Quote: -I- PndMCTrackAssociator::Init [INFO ] Branch: STTHitMix not found in Tree [INFO ] Branch: STTHitMix not found in Tree -W- PndMCTrackAssociator::Init: Using STTHit array [INFO ] Branch: MVDHitsStripMix not found in Tree [INFO ] Branch: MVDHitsStripMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsStrip array [INFO ] Branch: MVDHitsPixelMix not found in Tree [INFO ] Branch: MVDHitsPixelMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsPixel [INFO ] The number of entries in chain is 10 Found Tracks: 21 in event no. 0 ---------------- Track 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 Track 1 EntryNr: 0 EntryNr: 0 EntryNr: 0 [same for tracks 2-19] Track 20 EntryNr: 0 EntryNr: 0 EntryNr: 0 EntryNr: 0 *** Break *** segmentation violation =========================================================== There was a crash. This is the entire stack trace of all threads: =========================================================== Thread 1 (process 34695): #0 0x00007fff82fc1168 in wait4 () #1 0x00007fff8c4255f5 in system () #2 0x00000001000d6ca8 in TUnixSystem::Sta…
creator: Gianluigi Boca
date: 2012-07-24T13:16:09-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: The macro are the usual standard from macro/pid ,nothing new is added
creator: StefanoSpataro
date: 2012-07-24T13:22:44-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: Hello Gianluigi, Gianluigi Boca wrote on Tue, 24 July 2012 15:16 To be certain, first of all please show me the exact Macro you are using, thanks I'm using the macro delivered with the current SVN revision of the july12 release (rev 16248). But for the sake of completeness the contents of the run_reco_sttcombi.C: Show file content { // ======================================================================== // Verbosity level (0=quiet, 1=event level, 2=track level, 3=debug) Int_t iVerbose = 0; // Input file TString inDigiFile = "digi_sttcombi.root"; TString inSimFile = "points_sttcombi.root"; // Parameter file TString parFile = "params_sttcombi.root"; // Output file TString outFile = "reco_sttcombi.root"; // Number of events to process Int_t nEvents = 0; // ---- Load libraries ------------------------------------------------- gROOT->LoadMacro("$VMCWORKDIR/gconfig/rootlogon.C"); rootlogon(); TString sysFile = gSystem->Getenv("VMCWORKDIR"); // ------------------------------------------------------------------------ // In general, the following parts need not be touched // ======================================================================== // ----- Timer -------------------------------------------------------- TStopwatch timer; timer.Start(); // ------------------------------------------------------------------------ // ----- Digitization run ------------------------------------------- FairRunAna *fRun= new FairRunAna(); fRun->SetInputFile(inDigiFile); fRun->AddFriend(inSimFile); fRun->SetOutputFile(outFile); FairGeane *Geane = new FairGeane(); fRun->AddTask(Geane); // ------------------------------------------------------------------------ // ----- Parameter database -------------------------------------------- TString allDigiFile = sysFile+"/macro/params/all.par"; FairRuntimeDb* rtdb = fRun->GetRuntimeDb(); FairParRootFileIo* parInput1 = new FairParRootFileIo(); parInput1->open(parFile.Data()); FairParAsciiFileIo* parIo1 = new FairParAsciiFileIo(); parIo1->open(…
creator: André Zambanini
date: 2012-07-24T13:24:46-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: Andre', could you please go in your directory $VMCWORKDIR/sttmvdtracking and do : svn list -v PndSttMvdTracking.cxx and tell me please what is the version of the class corresponding to your release ? Thanks
creator: Gianluigi Boca
date: 2012-07-24T14:24:00-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: The output: andre@andre-macbook:~/Development/fairsoft/jan12/pandaroot_july12/sttmvdtracking$ svn list -v PndSttMvdTracking.cxx 15639 gboca 482898 Mai 29 00:23 PndSttMvdTracking.cxx Thanks so far!
creator: André Zambanini
date: 2012-07-24T15:42:06-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: hello Andre', then yes, you are using the most updated version. From the printout of your crash is difficult to guess what's wrong; the most efficient way to cure the problem would be for me to use your directory and do some printouts for debugging. Please let me know if that's possible Gianluigi André Goerres wrote on Tue, 24 July 2012 17:42 The output: andre@andre-macbook:~/Development/fairsoft/jan12/pandaroot_july12/sttmvdtracking$ svn list -v PndSttMvdTracking.cxx 15639 gboca 482898 Mai 29 00:23 PndSttMvdTracking.cxx Thanks so far!
creator: Gianluigi Boca
date: 2012-07-24T16:42:00-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: Hello Gianluigi, sorry, but since this is my private notebook, I'm not feeling comfortable with giving other persons access to it. I will have a look if I can find more information for the reason of the crash. If I find something, I will post it here. Thanks anyways.
creator: André Zambanini
date: 2012-07-25T07:26:49-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: ok Andre', I understand. We can try then the following alternative way (that almost never works in actuality). When you have time and possibility you please send me the root files you produced in generation and digitization and I try and see if I can reproduce your crash thanks in advance Gianluigi André Goerres wrote on Wed, 25 July 2012 09:26 Hello Gianluigi, sorry, but since this is my private notebook, I'm not feeling comfortable with giving other persons access to it. I will have a look if I can find more information for the reason of the crash. If I find something, I will post it here. Thanks anyways.
creator: Gianluigi Boca
date: 2012-07-25T11:03:51-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: The compressed files are attached. -André
creator: André Zambanini
date: 2012-07-25T11:51:02-00:00

Re: Crash in reco-macro, PndSttMvdTracking.cxx produces segfault
type: item
description: I just tested two other macro chains from the untouched SVN release. The one in the macro/sttmvdtracking/ folder is also breaking after the first event, the one in macro/emc/ is running through. This seems reasonable, since the segmentation violation output claims an error in the PndSttMvdTracking.cxx and the EMC probably doesn't use this.
creator: André Zambanini
date: 2012-07-25T13:50:28-00:00