Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

IDB doesn't work under Mac OS X

mattnotting
Beginner
1,011 Views
I got an interesting problem on my desktop minimac. It has a Mac OS 10.7.2 system. I installed a trial version of Intel Fortran Composer XE 2011 for Mac OS. I just wrote a simple fortran program fout.f90 to test it. The program is


program fout
implicit none
write(*,*) 'Hello'
stop
end
ifort works fine. It can generate a executable that can be run. However, when I use
idb fout
it tells me that
Intel Debugger for applications running on Intel 64, Version 12.1, Build [76.205.11]
------------------
object file name: fout
Reading symbols from /Users/jgeng/fout...done.
Could not start process for fout
No image loaded ... Recovering ...
I've checked the intel forum to try to find the problem solution. It seems there is no answer for this. IDB seems to read successfully the debug symbols, but fails to start. Interestingly, GDB can start normally. Why?????
Could anybody help me? Thanks
Jianghui
0 Kudos
3 Replies
Ron_Green
Moderator
1,011 Views
Yes, this is indeed a bug. I will start a bug report.

ron
0 Kudos
Ron_Green
Moderator
1,011 Views
THere is a workaround:

ifort -g -save-temps -fpic -Wl,-no_pie -o hello hello.f90

idb ./hello

I have a bug report started and am escalating this issue.

ron
0 Kudos
Georg_Z_Intel
Employee
1,011 Views
Hello,

I'd like to add the following information for clarification:
IDB cannot debug PIE enabled applications, neither for Linux* nor for Mac OS* X. For the latest Mac OS* X 10.7 (Lion) PIE is the default.
Hence if you want to debug an application it must be built without PIE explicitly. Please note that release versions still can and should be built with the default (PIE enabled).

Usually you'd turn off PIE with -fno-pie switch; unfortunately this switch is broken for Intel C/C++ & FORTRAN Compiler and hence you have to provide -fpic -Wl,-no_pie as workaround. We're currently working on that (DPD200225616).

Sorry for the inconvenience & best regards,

Georg Zitzlsberger
0 Kudos
Reply