Stack trace in CLING

In a rare case I use Cling.

From a stack trace starting somewhere in a library

#39 0x00007f011b5132d0 in TRint::ProcessLineNr(char const*, char const*, int*) () from /cvmfs/
#40 0x00007f011b514647 in TRint::Run(bool) () from /cvmfs/
#41 0x00000000004010dc in main ()

it is very difficult to tell from which line in the script the crash originated.

Is there anything analogous to the -g option of g++?

Apparently we don’t have a way to display the crashes from the JIT.
You can try to use ACLIC adding a trailing + to the script file name when including it.


1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.