|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
07 Jun 2007, Randolf Pohl, Forum, crash when analyzing multiple runs offline
|
08 Jun 2007, Stefan Ritt, Forum, crash when analyzing multiple runs offline
|
09 Jun 2007, Randolf Pohl, Forum, crash when analyzing multiple runs offline
|
10 Jun 2007, Stefan Ritt, Forum, crash when analyzing multiple runs offline
|
11 Jun 2007, Randolf Pohl, Forum, crash when analyzing multiple runs offline
|
11 Jun 2007, Stefan Ritt, Forum, crash when analyzing multiple runs offline
|
12 Jun 2007, Randolf Pohl, Forum, crash when analyzing multiple runs offline
|
|
Message ID: 385
Entry time: 08 Jun 2007
In reply to: 382
Reply to this: 386
|
Author: |
Stefan Ritt |
Topic: |
Forum |
Subject: |
crash when analyzing multiple runs offline |
|
|
Unfortunately I don't have time right now to debug the problem, but I could see
roughly what it could be. The analyzer crashes inside CloseRootOutputFile:
#5 <signal handler called>
#6 0x00002b5f52ad5ee5 in free () from /lib64/libc.so.6
#7 0x000000000040c89b in CloseRootOutputFile () at src/mana.c:1489
in the line
free(tree_struct.event_tree[i].branch);
If a "free" crashes, it might indicate that the memory beyond the allocated space
got corrupted. The branch gets allocated in book_ttree(), once for each
analyze_request[i]. The branch gets filled in write_event_ttree():
/* fill tree both online and offline */
if (!exclude_all)
et->tree->Fill();
Maybe one should put printf debugging statements in these places to see what's
going on. |