RE: CINT problem?

From: Philippe Canal <pcanal_at_fnal.gov>
Date: Sun, 30 Apr 2006 13:29:39 -0500

> since I have compiled the macro with .L (in the ROOT session), I have
> compiled it with ACLiC, haven't I?

As long as you also added the trailing '+'.

> And it ended successfully...

Then it is a bug in CINT.

> BTW, in case it is a problem of CINT, what should I do?

For now, work-around the problem by compiling using ACLiC. Also if you get a change you could send us a __standalone__ complete, running example so that we can reproduce the problem and eventually insure that it is fixed.

Cheers,
Philippe.

> I cannot install since I work on a machine of which I am not the
> administrator

Note that you do not need to be an administrator to install and use valgrind.

-----Original Message-----
From: owner-roottalk_at_pcroot.cern.ch [mailto:owner-roottalk_at_pcroot.cern.ch] On Behalf Of Chiara.Zampolli_at_bo.infn.it
Sent: Sunday, April 30, 2006 3:55 AM
To: Philippe Canal
Cc: roottalk_at_pcroot.cern.ch
Subject: RE: [ROOT] CINT problem?

Dear Philippe,

    since I have compiled the macro with .L (in the ROOT session), I have compiled it with ACLiC, haven't I? And it ended successfully... As I have written in my previous mail, I have tried also to debug it with gdb, and no stack was created... Only valgrind (which I do not have installed at the moment, and I cannot install since I work on a machine of which I am not the administrator) remains... BTW, in case it is a problem of CINT, what should I
do?

Thank you for your help.
Regards,
Chiara

Quoting Philippe Canal <pcanal_at_fnal.gov>:

> Hi,
>
> If your code works succesfully when compiled by ACLiC then
> this is a CINT problem (either a CINT byte optimization
> problem or a problem with interpreted stl container).
>
> If you code fails when compiled by ACLiC then try
> running with valgrind or the debugger (gdb).
>
> Cheers,
> Philippe
>
> -----Original Message-----
> From: owner-roottalk_at_pcroot.cern.ch [mailto:owner-roottalk_at_pcroot.cern.ch]
> On Behalf Of Chiara Zampolli
> Sent: Friday, April 28, 2006 5:13 AM
> To: roottalk
> Subject: [ROOT] CINT problem?
>
> Dear rooters,
>
> I am running a macro (see the attched file) which loops over some
> events (from event 0 to event 49) generated with AliRoot (ROOT version =
> v5-08-00, AliRoot = head version of Nov 1st 2005). When running it, it
> crashes with the error message:
>
> ------------------------------------
> ----------FILE =
>

/exports1/aliprod1/zampolli/ProdNewHEAD/Hij_5fm.Run1/Events/Hij_5fm.Evt40---
> -------------------
> ------------------------------------
> rl = 0x9ad44340
> ********* Processing event number: 0*******
> Number of ESD tracks : 17415
> stack = 0x9e856a98
> npart = 586373
> sono qui ciccina!!
> sono qui ciccina 1 !!
> ------------------------------------
> ----------FILE =
>

/exports1/aliprod1/zampolli/ProdNewHEAD/Hij_5fm.Run1/Events/Hij_5fm.Evt41---
> -------------------
> ------------------------------------
> rl = 0xba2fbdc8
> Syntax Error: * momrec2events.C:237:
> Error: Illegal pointer operation (tovalue) momrec2events.C:237:
> *** Interpreter error recovered ***
> root [1] .q
>
> NB: in the version of the macro I have attached, some of the print-outs
> have been suppressed, so that line 236 corresponds to line 190.
>
> I'm not sure this is a problem with ROOT, but... could it be a problem
> of CINT? I have successfully compiled the macro (.L momrec2events.C++),
> and tried also with the gdb debugger, but "No stack" has been produced,
> so I don't know what else I should do...
>
> Do you have any suggestion?
> Thank you in advance.
> Best Regards,
> Chiara
>
>

---

This message was sent using IMP, the Internet Messaging Program. Received on Sun Apr 30 2006 - 20:41:26 MEST