Back Midas Rome Roody Rootana
  Root Display GUI  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
Entry  02 Mar 2008, Exaos Lee, Bug Report, ROODY kills analyzer too!! 
    Reply  03 Mar 2008, Randolf Pohl, Bug Report, ROODY kills analyzer too!! crash-analyzer.txtcrash-roody.txtroody-tarball-dir.txt
       Reply  04 Mar 2008, Exaos Lee, Bug Report, Revision 221 works! But not remotely.  
          Reply  07 Mar 2008, Randolf Pohl, Bug Report, Revision 221 works! But not remotely.  
             Reply  07 Mar 2008, Stefan Ritt, Bug Report, Revision 221 works! But not remotely.  
    Reply  17 May 2009, Randolf Pohl, Bug Fix, [PATCH] ROODY kills analyzer too!! 
       Reply  23 Jul 2009, Exaos Lee, Bug Fix, [PATCH] ROODY kills analyzer too!! 
Message ID: 135     Entry time: 03 Mar 2008     In reply to: 134     Reply to this: 137
Author: Randolf Pohl 
Topic: Bug Report 
Subject: ROODY kills analyzer too!! 
Hi,

I had the very same problem last summer during our beam time. Don't know the revision, but it was the tarball I downloaded around mid-July.
Symptom: The MIDAS (online) analyzer crashed as soon as roody was started. Started, i.e. before any user interaction became even possible. And the crash happened always. 100.0%.

My workaround was: Use roody rev. 220.
No crashes, beam time saved.

I attach 2 outputs I saved at that time.

Oh, yes: I still have the sources and such. Last modified date is July 9 and earlier (see attachment 3). I can send them around if you want to find the revision and bracket the offending commits. (I wish you were using "git". Ever read about git-bisect?)

Cheers,

Randolf

PS: Konstantin, I had promised you to try and pin down the problem after the run. Obviously I forgot, sorry. Please tell me if I can be of any help now.
Attachment 1: crash-analyzer.txt  2 kB  | Show | Hide all | Show all
Attachment 2: crash-roody.txt  698 Bytes  | Hide | Hide all | Show all 
Lamb_be>roody -h localhost
main.cxx: Re-executing 'roody' with compiled-in ROOTSYS='/usr/local/root'
SetOptStat("nemri") got 1001111
Unable to open file "default.xml": No such file or directory
ReadRemoteObject trig_start from folder histos
Folder histos pointer 0
ReadRemoteObject trig_pattern from folder histos
ReadRemoteObject trig_tdc from folder histos
SysError in <TUnixSystem::UnixSend>: send (Broken pipe)
ReadRemoteObject trig_adc from folder histos
ReadRemoteObject trig_detector from folder histos
ReadRemoteObject trig_fadc from folder histos
ReadRemoteObject trig_cool from folder histos
ReadRemoteObject trig_display from folder histos
ReadRemoteObject lambdameter from folder histos
Attachment 3: roody-tarball-dir.txt  1 kB  | Show | Hide all | Show all
ELOG V3.1.4-2e1708b5