Intel® Parallel Studio XE 2015 Update 7 Composer Edition for Windows* includes the latest update of the Intel Fortran and C/C++ 15.0 compilers for IA-32 and Intel® 64 architecture systems.
Trying out 2017 beta version of Fortran (I also have the previous 2013 ifort version) but I'm having a challenge with gdb-ia. I have my .bash_profile set so that DYLD_LIBRARY_PATH is set so that on the command line I get
When in gdb-ia I get the following
(gdb) set environment DYLD_LIBRARY_PATH /opt/intel/compilers_and_libraries_2017.0.039/mac/compiler/lib
When i unlock certificate pop up window certificate unlocked. But when i build my app window show that certificate still lock
when using gdb I normally use it inside Emacs, which provides a nice environment for debugging while in text mode (image attached), but this doesn't seem to work with gdb-ia. When invoking gdb from inside Emacs, I change the name of the gdb executable to gdb-ia, but I get the error:
angelv@carro:~$ Error: you did not specify -i=mi on GDB's command line!
Is there any way to get gdb-ia to play nicely with GDB Emacs mode?
Ángel de Vicente
I am using Intel Visual Fortran Composer XE 2013 SP1 Update 6 for Windows, Version 2013.1.6.241, with Visual Studio 2013 on Windows 7. I created a default "Hello World" console application and added a single local variable, integer i. The Win32 Debug build allows me to step through with the debugger and view the value of i where I added it in the Watch 1 window. So far, so good. I then used the Configuration Manager to add builds for x64, copying settings from Win32. When I now build and debug the x64 Debug configuration, I cannot view the value of i.
I am trying to debug a C++ application with gdb-ia, but some functions are missing debug information (while other functions are ok).
All files are compiled with the same compiler options. This is an extract from the Makefile:
I have been searching around and I have come so far as to find that one can have access to module variables in the watch window through modulename::variable, which helps.
Is it possible to get this as a mouse-over as well? We have a large code base with legacy code so it happens that one has to debug unfamiliar code. It is very useful to be able to glance through variables to see what they contain. It is possible to use the watch window, but it takes much longer time.
I was building a program with ifort, however at the lingking stage, it was reported that 'ld: cannot find -lm'
How to solve this?
I was buiding a program with ifort and at linking stage I received such report.
How to solve this?
I am porting a program with VB6 UI + Compac DLL to VB.NET 2013 + Intel Fortran (11.1) DLL
A small dummy program, in VS 2 projects (UI and DLL), works fine, i.e.:
- data input in UI
- data changed in DLL
- changed data displayed in UI
I'm using the following configuration:
- VS 2013
- Intel Frotran 11.1 for windows
- IMSL 7-1