Home » PANDA » PandaRoot » Bugs, Fixes, Releases » problem running reco macro with the july12 release
problem running reco macro with the july12 release [message #13838] |
Thu, 02 August 2012 16:49 ![Go to next message Go to next message](/theme/gsi/images/down.png) |
Karin Schönning
Messages: 65 Registered: August 2012 Location: Uppsala University
|
continuous participant |
From: *tsl.uu.se
|
|
Hi,
I checked out and compiled the jul12 release of pandaroot (revision 16335) on my local machine (Ubuntu 12.04). This worked fine except that I had to check out the geant3 libraries separately (does that matter?).
I also managed to run the tasks in pandaroot/tutorials/feb12 (from generation/transport to analysis) for 100 events which worked fine. However, when trying 1000 events, the reco task crashed after 257 events. The log (with verbose mode 1) is in the attached file. My colleague does not reproduce this crash (the only difference, as far as I can see, is that her machine is Ubuntu 10.04). Does anybody have an idea about what the reason for the crash could be and what I could do about it?
Kindest regards,
/Karin
-
Attachment: log1
(Size: 1.36MB, Downloaded 235 times)
|
|
|
Re: problem running reco macro with the july12 release [message #13840 is a reply to message #13838] |
Thu, 02 August 2012 18:10 ![Go to previous message Go to previous message](/theme/gsi/images/up.png) ![Go to next message Go to next message](/theme/gsi/images/down.png) |
StefanoSpataro
Messages: 2736 Registered: June 2005 Location: Torino
|
first-grade participant |
![theavatar_ss](/theme/gsi/images/skype.png) From: *31-79-r.retail.telecomitalia.it
|
|
Dear Karin,
about geant3 installation, I had the same problem with my Ubuntu 12.04, hopefully fairroot experts will solve such problem.
About your crash, your log does not help so much because all the backtrace is missing.
First of all, I would suggest to run the reco again to see if the error is appearing again at the same event number.
If you want to run less events, in the reco macro you could use:
to run events from 250 to 260, in order to be faster.
If the error occurs again, I would suggest to run gdb and to post the backtrace.
This means, from your macro folder:
> gdb root.exe
...
> r (from the gdb shell)
...
> .x run_reco_sttcombi.C (from root)
...
after the crash, type
> bt
and copy what comes after.
|
|
|
Re: problem running reco macro with the july12 release [message #13864 is a reply to message #13838] |
Fri, 10 August 2012 12:29 ![Go to previous message Go to previous message](/theme/gsi/images/up.png) ![Go to next message Go to next message](/theme/gsi/images/down.png) |
Karin Schönning
Messages: 65 Registered: August 2012 Location: Uppsala University
|
continuous participant |
From: *tsl.uu.se
|
|
Hi Stefano,
I have been away and could not perform the check until now, however, thanks for your response. When running from event 1 it always crashes at the same event, namely 257, but when starting at i.e. event 250 it does not crash at 257 but continues as long as I wish (as it seems). Running the debugger gives the following output:
******* event # 257*******
PROBLEM HAS NO FEASIBLE SOLUTION
Program received signal SIGBUS, Bus error.
0x00007fffe621fe2a in PndSttMvdTracking::Exec (this=0x7fffe1bf4010,
opt=0x7fffeaed5a30 "")
at /home/schonnin/panda/pandaroot/sttmvdtracking/PndSttMvdTracking.cxx:4093
4093 dis=sqrt( Oxx*Oxx+Oyy*Oyy );
(gdb) bt
#0 0x00007fffe621fe2a in PndSttMvdTracking::Exec (this=0x7fffe1bf4010,
opt=0x7fffeaed5a30 "")
at /home/schonnin/panda/pandaroot/sttmvdtracking/PndSttMvdTracking.cxx:4093
#1 0x00007ffff753139d in TTask::ExecuteTasks (this=0x649e40,
option=0x7fffeaed5a30 "")
at /home/schonnin/panda/jan12/tools/root/core/base/src/TTask.cxx:312
#2 0x00007ffff753117d in TTask::ExecuteTask (this=0x649e40,
option=0x7fffeaed5a30 "")
at /home/schonnin/panda/jan12/tools/root/core/base/src/TTask.cxx:275
#3 0x00007fffeadff42a in FairRunAna::Run (this=0x649be0, Ev_start=0,
Ev_end=1000) at /home/schonnin/panda/pandaroot/base/FairRunAna.cxx:544
#4 0x00007fffeae712b3 in G__G__BaseDict_986_0_6 (result7=0x7fffffff2a80,
funcname=0x644d40 "", libp=0x7ffffffe8070, hash=0)
at /home/schonnin/panda/pandaroot/buildPanda/base/G__BaseDict.cxx:14827
#5 0x00007ffff59a5e81 in Cint::G__ExceptionWrapper (
funcp=0x7fffeae711ae <G__G__BaseDict_986_0_6(G__value*, char const*, G__param*, int)>, result7=0x7fffffff2a80, funcname=0x644d40 "", libp=0x7ffffffe8070,
hash=0) at cint/cint/src/Api.cxx:393
#6 0x00007ffff5a7e3fb in G__execute_call (result7=0x7fffffff2a80,
libp=0x7ffffffe8070, ifunc=0x644d40, ifn=0)
at cint/cint/src/newlink.cxx:2406
#7 0x00007ffff5a7ed9d in G__call_cppfunc (result7=0x7fffffff2a80,
libp=0x7ffffffe8070, ifunc=0x644d40, ifn=0)
---Type <return> to continue, or q <return> to quit---
|
|
|
|
|
Goto Forum:
Current Time: Mon Sep 02 20:17:14 CEST 2024
Total time taken to generate the page: 0.00834 seconds
|