If you add more elements to the big ntuple in ntuple.C, one day you will
see this message:
Limitation: Statement too long FILE:ntuple.C LINE:44
cint: Security mode 0x7:0x2 *** Fatal error in interpreter...
restarting interpreter ***
*** Fatal error in interpreter... restarting interpreter ***
I saw this in August and reproduced this error just now. If you look at
the numbers I listed in an earlier message, the string is way from
overflow yet however, ROOT can not handle it. We will see this error again
when we add more and more entries into it. One day we may have to make the
decision to change the structure of this ntuple and change all the
relevant codes.
This makes me think that Draw() may not be able to handle a long string
either. I am not sure. I have to run the macro, generate and locate the
error.
On Mon, 28 Oct 2002, Aaron Joseph Maschinot wrote:
>
> I didn't look tooooooo closely at the string that was providing the seg
> fault last night. However, I seem to remember that there were many blank
> places in the string, e.g. (ttl12 > 0) as opposed to (ttl12>0).
>
> Surely, it's not a permanent solution, but, in the interest of just
> getting a correct result as soon as possible (for commissioning purposes),
> maybe TBLCut (or whatever is causing the problem) should be modified to
> take out non-essential blank spaces in the cuts.
>
> Or perhaps this idea is totally wrong...
>
> Aaron
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST