icc Compiler 13 segfaults

icc Compiler 13 segfaults

Steven C.'s picture

I installed the currently available Composer software (l_ics_2013.0.028.tgz) on a Debian 7 system.

Attempts to use the C compiler generates on error

$ icc -v

Segmentation fault

$ gcc -v

gcc version 4.7.2 (Debian 4.7.2-5)

19 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.
Steven C.'s picture

Problem is not resolved by applying Intel® C++ Composer XE for Linux* Version 2013 (Update 5).

Traceback from gdb:

Starting program: /apps/share64/debian7/intel/intel-13.0.028/bin/icc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7ff5e00 in db_version ()
   from /apps/share64/debian7/intel/intel-13.0.028/composer_xe_2013.5.192/bin/intel64/libintelremotemon.so
(gdb) where
#0  0x00007ffff7ff5e00 in db_version ()
   from /apps/share64/debian7/intel/intel-13.0.028/composer_xe_2013.5.192/bin/intel64/libintelremotemon.so
#1  0x00007ffff5ee6bc0 in __env_attach () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#2  0x00007ffff5ee15f1 in __env_attach_regions () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#3  0x00007ffff5ee1e08 in __env_open () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#4  0x00007ffff616326c in ?? () from /usr/lib/libnss_db.so.2
#5  0x00007ffff616192a in ?? () from /usr/lib/libnss_db.so.2
#6  0x00007ffff6161c16 in _nss_db_getprotobyname_r () from /usr/lib/libnss_db.so.2
#7  0x00007ffff728e84d in __getprotobyname_r (name=0x677410 "tcp", resbuf=0x7ffff7523890, buffer=0x9adb10 "\250\022R\367\377\177",
    buflen=1024, result=<optimized out>) at ../nss/getXXbyYY_r.c:256
#8  0x00007ffff728e6a0 in getprotobyname (name=0x677410 "tcp") at ../nss/getXXbyYY.c:117
#9  0x0000000000470f9f in ?? ()
#10 0x00000000004713ff in Ox34b3c8b0408f1827 ()

#11 0x000000000044b27b in Ox34b3d0e94e2b0630 ()
#12 0x000000000048e9b7 in ?? ()
#13 0x000000000048f06c in Ox34b3ca5208d4bbc6 ()
#14 0x000000000047aa31 in ?? ()
#15 0x000000000047b485 in Ox34b3cc4d23b4f6b1 ()
#16 0x000000000047b754 in Ox34b3cc225160db74 ()
#17 0x000000000047b977 in Ox34b3cc2a32c765a1 ()
#18 0x0000000000430ea2 in Ox34b3d2e814454707 ()
#19 0x000000000043cbf6 in Ox34b3de9263fbc4f3 ()
#20 0x000000000043d152 in lc_next_conf ()
#21 0x00000000004fbbde in checkout_license ()
#22 0x00000000004fb5b1 in flex_checkout_license ()
#23 0x00000000004cf62a in driver_license_checkout ()
#24 0x00000000004bbbb7 in main ()

Sergey Kostrov's picture

>>Attempts to use the C compiler generates on error
>>
>>$ icc -v
>>
>>Segmentation fault
>>
>>$ gcc -v

I'd like to confirm that only -v command line option without any C or C++ source files were used for both compilers. Thanks.

>>...
>>#21 0x00000000004fbbde in checkout_license ()
>>#22 0x00000000004fb5b1 in flex_checkout_license ()
>>#23 0x00000000004cf62a in driver_license_checkout ()
>>...

Please verify that Flex Licensing Service is working and all licenses are valid.

Steven C.'s picture

I can confirm that both icc and gcc commands were both simple attempts to report version (no more command line arguments).  The icc command also seg faults when no options and supplied on the command line.

The Flex Licensing Service works with with the 2012 version of icc and the same license file.

Sergey Kostrov's picture

One more question: Did you try the same tests when logged as a Root user?

sukruth-v (Intel)'s picture

Hi Steven,

               As Sergey pointed out, This seems more likely an issue with FlexLM. Could you please submit an issue to premiersupport.intel.com (Download, Licensing and Registration product type), As forum is not right place to discuss about the confidential information like SN's.

Regards,

Sukruth H V

Steven C.'s picture

I do not have root access on the machine in question and the compiler software was was installed as a non-root user.

Steven C.'s picture

Is this the correct site?  https://premier.intel.com/premier/     The address premiersupport.intel.com was not locateable. 

The Intel® Premier Support site will be down Thursday, August 15th 6pm PDT to Sunday, August 18th 5pm PDT due to system maintenance activities. During this maintenance you will have no access to your issues.

Steven C.'s picture

I do not hace root access on the host in question.  The software was installed as user apps.  The icc command fails as user apps.

Brandon Hewitt (Intel)'s picture

Hi Steven,

That path name: "/apps/share64/debian7/intel/intel-13.0.028/bin/icc" implies a package number of 13.0.028 which would be an extremely early pre-release of the 13.0 compiler. The initial product release was 13.0.079.

That being said, the current 13.0/13.1 compilers don't support Debian 7*. You may want to try the beta compiler by signing up in the stickied thread at the top of the forum. Note that the beta is pretty much wrapped up at this point, but it should get you going until the product release for Intel(R) Composer XE 2013 SP1 (i.e. compiler 14.0) comes out.

Brandon Hewitt Technical Consulting Engineer Tools Knowledge Base: "http://software.intel.com/en-us/articles/tools" Software Product Support info: "http://www.intel.com/software/support"
Steven C.'s picture

The directory intel-13.0.028 was my doing based on the downloaded (l_ics_2013.0.028.tgz) evaluation copy of Intel® Cluster Studio XE for Linux*.   The actual underlying composer directory is composer_xe_2013.1.117.

The lack of Debian 7 support is disappointing given that it was released months ago.  Perhaps I will try the beta version as suggested.

Steven C.'s picture

The installer was unable to recognize the system as a Debian 7 installation.

Detected operating system is not supported. Supported operating systems for this
release include:
    - Red Hat Enterprise Linux* 7, 5, 6;
    - Debian* 6.0, 7.0;
    - Fedora* 18, 19;
    - SuSE SLES* 10, 11;
    - Ubuntu* 12.04, 13.04;

It would be nice if it mentioned what operating system it did detect.

The installer also reported that it could not find various 32-bit libraries.

32-bit libraries not found on this system.
This product release requires the presence of 32-bit compatibility libraries
when running on Intel(R) 64 architecture systems. One or more of these libraries
could not be found:
    libstdc++ (including libstdc++6)
    glibc
    libgcc
Without these libraries, the compiler and the debugger will not function
properly.  Please refer to Release Notes for more information.

The behavior is same for the 2013 beta version.

$ bash
$ source intel-2013/bin/compilervars.sh
$ source intel-2013/bin/compilervars.sh intel64
$ which icc
/apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/bin/intel64/icc
$ which gdb
/apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/debugger/gdb/intel64/py27/bin/gdb
$ icc
Segmentation fault
$ gdb `which icc`
No symbol table is loaded.  Use the "file" command.
GNU gdb (GDB) 7.5-1.0.152
Copyright (C) 2012 Free Software Foundation, Inc; (C) 2013 Intel Corp.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For information about how to find Technical Support, Product Updates,
User Forums, FAQs, tips and tricks, and other support information, please visit:
<http://www.intel.com/software/products/support/>...
Reading symbols from /apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/bin/intel64/icc...done.
(gdb) r
Starting program: /apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/bin/intel64/icc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7ff4e00 in db_version ()
   from /apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/bin/intel64/libintelremotemon.so
(gdb) where
#0  0x00007ffff7ff4e00 in db_version ()
   from /apps/share64/debian7/intel/intel-2013/composer_xe_2013_sp1.0.051/bin/intel64/libintelremotemon.so
#1  0x00007ffff5edebc0 in __env_attach () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#2  0x00007ffff5ed95f1 in __env_attach_regions () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#3  0x00007ffff5ed9e08 in __env_open () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#4  0x00007ffff615b26c in ?? () from /usr/lib/libnss_db.so.2
#5  0x00007ffff615992a in ?? () from /usr/lib/libnss_db.so.2
#6  0x00007ffff6159c16 in _nss_db_getprotobyname_r () from /usr/lib/libnss_db.so.2
#7  0x00007ffff728e84d in getprotobyname_r () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00007ffff728e6a0 in getprotobyname () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x0000000000470fcf in ?? ()
#10 0x000000000047142f in Ox34b3c8b0408f1827 ()
#11 0x000000000044b2ab in Ox34b3d0e94e2b0630 ()
#12 0x000000000048e9e7 in ?? ()
#13 0x000000000048f09c in Ox34b3ca5208d4bbc6 ()
#14 0x000000000047aa61 in ?? ()
#15 0x000000000047b4b5 in Ox34b3cc4d23b4f6b1 ()
#16 0x000000000047b784 in Ox34b3cc225160db74 ()
#17 0x000000000047b9a7 in Ox34b3cc2a32c765a1 ()
#18 0x0000000000430ed2 in Ox34b3d2e814454707 ()
#19 0x000000000043cc26 in Ox34b3de9263fbc4f3 ()
#20 0x000000000043d182 in lc_next_conf ()
#21 0x00000000004ff820 in conf_iterator(flex_lm_iterator_t*, char const*, char const*, int) ()
#22 0x00000000004fb649 in checkout_license(char const*, unsigned int, int, int, int, int, char const*) ()
#23 0x00000000004fb125 in driver_license_checkout() ()
#24 0x00000000004bc28c in main ()

Casey's picture

Quote:

Steven C. wrote:

The lack of Debian 7 support is disappointing given that it was released months ago.  Perhaps I will try the beta version as suggested.

It doesn't really matter if the distro is supported as long as you ensure you have the proper pre-requisiste development environment setup.  I run all of the intel compilers on Gentoo linux and the installaltion only requires that I choose to install on an unsupported OS.  

You can also avoid needing the 32bit libraries by only installing the 64 bit compilers i think, so if that is all you need you might try those packages instead of the combined 32/64 bit packages.

Steven C.'s picture

I did a fresh install without the 32-bit optional libraries but the results are the same.

kucerafzu.cz's picture

I have a similar problem with a fresh installation on a current debian/stable (7.3) system. The system is multiarch I installed only the 64-bit version:

    Intel(R) Fortran Compiler XE 14.0 Update 1                                  
        Intel Fortran Compiler XE for Intel(R) 64                               

    Intel(R) Debugger 13.0                                                      
        Intel Debugger for Intel(R) 64                                          

    Intel(R) Math Kernel Library 11.1 Update 1                                  
        Intel MKL core libraries for Intel(R) 64                                
        Intel(R) Xeon Phi(TM) coprocessor support                               
        Fortran 95 interfaces for BLAS and LAPACK for Intel(R) 64               
        GNU* Compiler Collection support for Intel(R) 64                        

    GNU* GDB 7.5                                                                
        GNU* GDB 7.5 on Intel(R) 64 (Provided under GNU General Public License  
v3)
        GDB Eclipse* Integration on Intel(R) 64 (Provided under Eclipse Public  
License v.1.0)

My gdb message is BELOW. Please note there is no reference to the flexlm which has worked with the previously installed version 11 (self-created alien-debian packages which, btw, still work in the debian 7.3 (wheezy) system.)

Any suggestion?

 

Jan

# gdb-ia ifort core
No symbol table is loaded.  Use the "file" command.
GNU gdb (GDB) 7.5-1.0.194
Copyright (C) 2012 Free Software Foundation, Inc; (C) 2013 Intel Corp.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For information about how to find Technical Support, Product Updates,              
User Forums, FAQs, tips and tricks, and other support information, please visit:
<http://www.intel.com/software/products/support/>...
Reading symbols from /opt/intel/composer_xe_2013_sp1.1.106/bin/intel64/ifort...(no debugging symbols found)...done.
[New LWP 5472]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `ifort'.
Program terminated with signal 11, Segmentation fault.
#0  0x00002ba9754bfe00 in db_version () from /opt/intel/composer_xe_2013_sp1.1.106/bin/intel64/libintelremotemon.so
(gdb) where
#0  0x00002ba9754bfe00 in db_version () from /opt/intel/composer_xe_2013_sp1.1.106/bin/intel64/libintelremotemon.so
#1  0x00002ba977531bc0 in __env_attach () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#2  0x00002ba97752c5f1 in __env_attach_regions () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#3  0x00002ba97752ce08 in __env_open () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#4  0x00002ba97722526c in ?? () from /usr/lib/libnss_db.so.2
#5  0x00002ba97722392a in ?? () from /usr/lib/libnss_db.so.2
#6  0x00002ba977223c16 in _nss_db_getprotobyname_r () from /usr/lib/libnss_db.so.2
#7  0x00002ba975ee284d in getprotobyname_r () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00002ba975ee26a0 in getprotobyname () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x000000000047105f in ?? ()
#10 0x00000000004714bf in ?? ()
#11 0x000000000044b33b in ?? ()
#12 0x000000000048ea77 in ?? ()
#13 0x000000000048f12c in ?? ()
#14 0x000000000047aaf1 in ?? ()
#15 0x000000000047b545 in ?? ()
#16 0x000000000047b814 in ?? ()
#17 0x000000000047ba37 in ?? ()
#18 0x0000000000430f62 in ?? ()
#19 0x000000000043ccb6 in ?? ()
#20 0x000000000043d212 in ?? ()
#21 0x0000000000500b40 in ?? ()
#22 0x00000000004fc935 in ?? ()
#23 0x00000000004fc4b1 in ?? ()
#24 0x00000000004d0173 in ?? ()
#25 0x00000000004bc476 in ?? ()
#26 0x00002ba975e0dead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#27 0x00000000004043e9 in ?? ()
#28 0x00007fffeb17b818 in ?? ()
#29 0x000000000000001c in ?? ()
#30 0x0000000000000001 in ?? ()
#31 0x00007fffeb17c501 in ?? ()
#32 0x0000000000000000 in ?? ()

 

kucerafzu.cz's picture

Interestingly enough the same installation seems to work on another computer with a similar configuration... and the same version of  /lib/x86_64-linux-gnu/libc.so.6 pinting to identical libc-2.13.so, the only difference I can see now... one (where it works) being a clean 64bit install in genuine intel, the other a multiarch installation on an AMD opteron .

 

I have to investigate the issue more deeply.

 

Jan

kucerafzu.cz's picture

Quote:

kucerafzu.cz wrote:

Interestingly enough the same installation seems to work on another computer with a similar configuration... and the same version of  /lib/x86_64-linux-gnu/libc.so.6 pinting to identical libc-2.13.so, the only difference I can see now... one (where it works) being a clean 64bit install in genuine intel, the other a multiarch installation on an AMD opteron .

 

I have to investigate the issue more deeply.

 

Jan

Final word: The system had gone through several Debian upgrades. I did a fresh install of Debian 7.3 on it after which the ifort does not give

segmentation Faults anymore.

 

iliyapolak's picture

It could be quite possible that bad pointer could have been passed from the second function (by looking at call stack).

iliyapolak's picture

@kucerafzu

Can you post register context?

Login to leave a comment.