Go to main content
Oracle® Developer Studio 12.6: Performance Library User's Guide

Exit Print View

Updated: July 2017
 
 

Run-Time Issues

At run time, if running with compiler parallelization, the Oracle Developer Studio Performance Library uses the same pool of threads that the compiler does. The per-thread stack size must be set to at least 8 Mbytes on all platforms. This is done with the STACKSIZE or the OMP_STACKSIZE environment variable (units in Kbytes). You cannot use both. If you use the two environment variables simultaneously and the two values are different, the program stops with an error message.

To set the per-thread stack size to 8 Mbytes :

my_host% setenv STACKSIZE 8192

Setting the STACKSIZE environment variable is not required for programs running with POSIX or Oracle Solaris threads. In this case, user-created threads that call Performance Library routines must have a stack size of at least 8 Mbytes. Failure to supply an adequate stack size for the Performance Library routines might result in stack overflow problems. Symptoms of stack overflow problems include runtime failures that could be difficult to diagnose. For more information on setting the stack size of user-created threads, see the pthread_create(3C), pthread_attr_init(3C), and pthread_attr_setstacksize(3C) man pages for POSIX threads or the thr_create(3C) for Oracle Solaris threads.


Tip  -  If you are having issues diagnosing a core dump, try increasing the stack size above the minimum.