ifort and mac IDE's: XCode 3 or Eclipse Photran

[ebm2134]

Hi Folks,

I know that there is support for eclipse on linux operating systems, but how can I get ifort to work with photran on the mac? Would it be easier to work with XCode 3?

Could anyone recommend any guides or tutorials?

From my experience with eclipse, it seems easier to import a preexisting project into eclipse than into XCode 3 and so I'd prefer if if I could get ifort and idb working with Photran.

Best,

Ed

[zuch]

you can use eclipse with makefile based projects but I do not think there is a support for idb.

idb integration plugin exist only for linux. if you chose Xcode you will have the same issue.

none of the IDE's are fully supported they serve as a fancy text editors with limited debugging options.

I hope new intel fortran will include idb support in Xcode.gdb maybe an alternative solution but i have had problems with fortran modules.

[ebm2134]

When you say problems with fortran modules, is it because during a breakpoint, variables defined in these modules and imported with a use statement are not displayed?

This is exactly the problem that I'm having that I was hoping if I moved to ifort/idb this would be fixed.

[Ron_Green]

There are technical limitations to the extensibility of Xcode preventing full integration of Intel Fortran and Intel IDB. Even in Xcode 4.1 we don't have the ability to do a full integration. So I would not expect what we call the "Limited feature" integration into Xcode to change anytime soon. It will remain essentially an editor for Fortran.

On Mac OS, there is the a command line version of IDB that you can use. IDB is fully Fortran aware. If something doesn't work (and we have a few open bugs currently) then we want to know so we can fix it. Yes, it is able to display module data, derived types, etc. as you would expect.

If you want a GUI, DDD can wrap IDB and work nicely. See this article: http://software.intel.com/en-us/forums/showthread.php?t=60060

ron

[ebm2134]

Ron,

DDD looks great. Much simpler and even cleaner with its crude X11 interface than what I've been finding with Eclipse.

Question though, is it possible to view variables declared as parameters?

[mecej4]

> is it possible to view variables declared as parameters?

I think that whether that is possible or not depends entirely on the availability of a switch to make the compiler output debug symbols for named constants, rather than on the GUI or the debugger. For example, the Windows version of IFort has /debug-parameters[:keyword] . See your compiler documentation.

[Ron_Green]

yes, compile with -g -debug-parameters all

the default is for the compiler to remove the parameter symbols and replace with constants that don't show in the debugger. -debug-parameters overrides this and leaves the symbols in.

ron

[ebm2134]

Glad to see such a flag exists, except now I'm getting the following when I load my program into ddd

[plain]The debugger could not perform a unusual relocation while reading the debug information; as a result, some information may not be available.
done.[/plain]

[sectionbodytext]
[/sectionbodytext]

[sectionbodytext]I didn't get this problem before I introduced the -debug-parameters all flag.[/sectionbodytext]

[sectionbodytext]
[/sectionbodytext]

[sectionbodytext]
[/sectionbodytext]

[sectionbodytext]Also, should this be successful, this warning aside, would I be able to view the variables by going to the Data menu -> Status Displays... -> And then selecting "All global and static variable names and those matching..." ???[/sectionbodytext]

[sectionbodytext]I ask, because doing so produces this in the GDB console:[/sectionbodytext]

[sectionbodytext]
graph display `    variables  `[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]and what appears in my Data window is:[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]This was occurring with or without the -debug-parameters all flag. It is what prompted me to ask my follow up questions about viewing parameters in the first place.[/sectionbodytext]
[sectionbodytext]
[/sectionbodytext]
[sectionbodytext]I should add that these parameters are being imported from a module with the USE statement, hence they are not local.[/sectionbodytext]

[Lorri_M_Intel]

Please try -debug-parameters used (instead of "all")

There is an amount of overhead (ie, a symbol table entry, debug entry) associated with debugging parameters; it sounds like you exceeded a memory limitation.


-- Lorri