|Message: Re: Run aborted: is a ROOT problem?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hello Maria Let me try to help anyway since you received no answer up so fare... > My simulation should create a ROOT file as output. Bad luck. > After running some hours, it aborts. Really ? > This are the error messages: > *** Break *** segmentation violation > Generating stack trace... > 0x407d74c7 in G__call_cppfunc + 0x2ba from /usr/local/cern/root/lib/libCint.so > .... bla bla, beurk, bla bla.... > 0x4010f06d in TApplication::Run(bool) + 0x37 from /usr/local/cern/root/lib/libCore.so > 0x4124c672 in TRint::Run(bool) + 0x380 from /usr/local/cern/root/lib/libRint.so > 0x08048e34 in main + 0x90 from /usr/local/cern/root/bin/root.exe > 0x4138a970 in __libc_start_main + 0xf0 from /lib/tls/i686/cmov/libc.so.6 > 0x08048d01 in TApplicationImp::ShowMembers(TMemberInspector&, char*) + 0x39 from /usr/local/cern/root/bin/root.exe > Can someone tell me what does it means? Yes ; you are in a mess. But don't worry, you are not alone. > What's the promblem? No comment. Ok, stop joking ; you have the nasty problem of using two big softwares, then the upper traceback may be a hell to debug. But in this particular case (crash in CINT) it seems to be a T-problem ; probably something wrong in a CINT script. It seems that the interpreter is unable to find some outside compiled code. Perhaps a crash in some of your end-of-job CINT script ? Else the crash seems to happen after hours (which is anyway a pain ; whatever the software used), then check the (expected) file size and available space on your disk.... Else you may have a memory leak problem ; check that your "new" have their pending "delete". (Use "top" to see if your job consume memory). Verify also your .rootrc for fancy plugins. Are you using some threading ? etc, etc, etc... Can't say more, but the best is definitely to try to get help at http://root.cern.ch ; the ball seems to be for the other camp. Browse for example the (hundred) of bug reports around cint. Else you can plan to jump in a train for CERN with your computer, they have a workshop next week... Regards
|Inline Depth:||Outline Depth:||Add message:|