{"id":2738,"date":"2017-10-31T09:53:23","date_gmt":"2017-10-31T09:53:23","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=2738"},"modified":"2021-04-27T11:10:42","modified_gmt":"2021-04-27T10:10:42","slug":"whats-cradle_errorstack","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/whats-cradle_errorstack\/","title":{"rendered":"What’s CRADLE_ERRORSTACK?"},"content":{"rendered":"

Environment Variable or Command-line Switch Stack-tracing<\/h2>\n

As with many complex products Cradle<\/em> monitors its internal operation and on the rare occasion that something goes wrong it writes information to a log. CRADLE_ERRORSTACK controls how much information is logged internally and output on these occasions.<\/p>\n

If in the unfortunate case a Cradle<\/em> tool crashes, there will often be a log produced in the %CRADLEHOME%\\logs\\errors directory<\/code>. This will enable 3SL<\/em> Support<\/em> to diagnose simple cases such as a lack of memory on the machine. If the case is more complex, the development team may need to know at which point the program was processing at the time the error occurred. CRADLE_ERRORSTACK<\/em> will enable additional internal logging that will output a simple execution stack trace into the log. This can aid diagnosis and resolution.<\/p>\n

Switching Stack Trace On and Off<\/h2>\n

CRADLE_ERRORSTACK<\/samp> is an environment variable. You can set it via the control panel’s Advanced system settings<\/strong> (see the screenshot).<\/p>\n

In Linux if you are editing the environment config files bashrc, profile, etc for either the system \/etc\/profile or the user ~\/.bashrc then use:<\/p>\n

export CRADLE_ERRORSTACK=true<\/pre>\n
Or as we now set CRADLEHOME in \/etc\/profile.d\/cradle.sh you can put the ‘CRADLE_ERRORSTACK=true’ variable in this file.<\/p>\n
Or you could start the Cradle<\/em> tool from within a command shell, (On Windows\u00ae) press windows<\/strong> key type cmd<\/code> and then in the shell set CRADLE_ERRORSTACK=true<\/code>, then launch the tool e.g. \"%CRADLEHOME%\\bin\\exe\\windows\\work.exe\"<\/code>. You can also set a -errorstack<\/code> parameter to your command line option, i.e. work.exe -errorstack<\/code> to start WorkBench<\/em> with the stack on.<\/p>\n
\"Turning
Environment Variables<\/figcaption><\/figure>\n
Should I leave CRADLE_ERRORSTACK on?<\/h3>\n
Generally there is no need to leave the stack trace on all the the time. There is a small performance hit if you do, so unless you are having problems we don’t advise you leave it enabled.<\/p>\n
What if that still does not sort the issue?<\/h3>\n
3SL Support may ask you to turn on tracing which produces a complete execution trail from the product. This has a large overhead and uses disk space and is only in used in the very trickiest of issues. Rest assured, it’s unlikely you’ll have to use\u00a0 it, but if you do there is a post here that explains tracing<\/a>.<\/p>\n
Article UpdateD<\/h5>\n
27\/04\/2021 \u2013 Using CRADLE_ERRORSTACK in Linux<\/p>\n