Intel® Threading Building Blocks - What You Should Know Before Requesting Technical Support

Submit New Article

Last Modified On :   September 19, 2008 1:00 AM PDT
Rate
 


Register for Support

To register for interactive support, please visit the Intel Software Development Products Registration Center web site. Registration will enable you to login into Intel® Premier Support and obtain interactive support along with product updates.

To get access to interactive support for Intel® Threading Building Blocks, you must register for one of these products:

  • Intel Threading Building Blocks for Windows*
  • Intel Threading Building Blocks for Linux*
  • Intel Threading Building Blocks for Mac OS*
What You Should Know Before Requesting Technical Support
  1. Submit the issue under the correct product name:
    The title of the product you registered for The name of the product to submit the issue
    Intel Threading Building Blocks for Windows* Intel Threading Building Blocks, Windows*
    Intel Threading Building Blocks for Mac OS* Intel Threading Building Blocks, Mac OS*
    Intel Threading Building Blocks for Linux* Intel Threading Building Blocks, Linux*
  2. Select the correct version of Operating System.

    On Microsoft Windows* systems, go to: Start » Programs » Control Panel » System » General

    On Linux* systems, execute cat /etc/issue command line.

    On Mac OS* system, execute /usr/bin/sw_vers.

    If you cannot find an entry in the drop down menu that exactly matches the operating-system version that you are using, then select Other and enter the OS version to the editable field Other Environment.
  3. Enter the appropriate customer impact value.
    Customer impact values include Low, Medium, High, and Showstopper and are defined as follows (listed from least to most important):
    • Low - An issue that has no significant impact and is submitted on a for-your-information basis.
    • Medium - An issue that does not stop development, however it needs to be fixed.
    • High - An issue with a short-term work-around, however it needs to be fixed as soon as p ossible.
    • Showstopper - An issue that prevents you from using Intel Threading Building Blocks.
  4. Give a complete development environment description.
    • Compiler Version: if you use Intel Compiler then version information may be obtained by running the compiler with the -V option; use -v to get the version of the GNU* Compiler
    • Build Platform: on Linux* and Mac OS* systems, execute "uname -m" command: i686 or i386 stand for IA-32, x86_64 stands for Intel 64 technology, and ia64 stands for Itanium™ Architecture; On Windows* systems go to: Start » Programs » Control Panel » System » General

    Tip: If you cannot find an entry in the drop down menu which exactly matches your settings then select Other and enter the your particular environment to the editable field Other Environment.

    Linux* and Mac OS* only:
    • Kernel Version: on either Linux* or Mac OS* system, enter an output from "uname -a" command line
    • Glibc Version: on Linux* systems, enter the output from the "rpm -q glibc" command OR use ldd command for your application and copy/paste complete versioned name of libc.so; on Mac OS* system, run "otool -L" command on your application and copy/paste complete version name of libSystem.*.dylib.
    • Libstdc++ Version: on Linux* system, enter the output from "rpm -q libstdc++" OR use ldd command on your application and copy/paste complete versioned name for libstdc++.so; on Mac OS* system, run "otool -L" command on your application and copy/paste complete version name of libstdc++.*.dylib.
  5. Give a complete problem description.
  6. Completely describe the build including:
    • All the build options used, or attach a .DSP, .VCPROJ, .ICPROJ or a make file
    • All third-party libraries or SDKs used along with their versions
    • Indicate whether you are using the debug or release version of the Intel Threading Building Blocks library.
  7. Provide a reproducible test case with clear, step-by-step instructions on how to use it along with a description of the expected behavior.
  8. Include exact details on the error.  If you can reproduce the problem with the debug build of Intel Threading Building Blocks library and get a message from the library, let us know. For example:
    Assertion v failed on line 1530 of file ../../../source/internal/Task.cppDetailed description: thread did not activate a task_scheduler_init object? Aborted
    The debug output may help us better understand your problem or give you a hint on how to fix the issue on your own. In the example above the library complains that a thread did not activate a task_scheduler_init object, which typically means that the thread did not initialize the library properly by instantiating its own task_scheduler_init object. Please, always attach a file with debug output to the problem description when it's possible.
  9. Provide other important data:
    • Any work-arounds that you are using
    • Any changes you can make that either fix or cause the issue
 




This article applies to: Intel® Threading Building Blocks Knowledge Base