idb does not work

[jungwukh]

Hello

Recently I purchased an intel fortran compiler for mac osx, and the debugger idb does not work.

The error message idb made is:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
/fea/ver11/main]> idb fea
Intel Debugger for applications running on Intel 64, Version 11.1,
Build [1.2097.2.263]
------------------
object file name: feap
Reading symbols from /Users/jwh/feap/ver11/main/fea...rm:
/var/folders/Lj/LjNInDDjHqa9yyj3IlZXME+++TI/-Tmp-/IDB-archive-extracts/Users-jwh-fea-ver11-Feap11_1mpi.a:
Too many open files
ar: /Users/jwh/feap/ver82/Feap11_1mpi.a: Too many open files

The system open-file limit has been reached.
So the debugger cannot open files it needs to read debug information.
The debugger's understanding of the program will be limited.

Unrecognized binary file format for file /Users/jwh/fea/ver11/Feap11_1mpi.a(celmt08.o)
Could not read debugging information from '/Users/jwh/fea/ver11/Feap11_1mpi.a(celmt08.o)'.
:
:(continues)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------

How can I resolve this problem?

Thanks,

Jung

[Kevin_D_Intel]

It appears this relates to the shell limit as discussed in this earlier thread (here). As per the earlier thread, try increasing the shell open files limit and retrying idb.

For bash/ksh use: ulimit -n and for csh/tcsh use: limit descriptors

Choose to reflect the number of object files you expect will be opened.

[jungwukh]

Quoting - Kevin Davis (Intel)

Hello Kevin,

Thank you for your anser.
I increased the descriptors as you mentioned, and met this message:


[jwh@jwimac:/Users/jwh/fea/ver11/main]> idb fea
Intel Debugger for applications running on Intel 64, Version 11.1, Build [1.2097.2.263]
------------------
object file name: fea
Reading symbols from /Users/jwh/fea/ver11/main/fea...Assertion failed: "found" src/st/mem/pil_loadablefileformatMachO.C:1831
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Could not start process for fea
No image loaded ... Recovering ...

Surely, my compiled file is in the directory, and I can run it. But I cannot load to idb.
I am using mac version of the fortran.
Could you help me further?

Thanks,
Jung

[Kevin_D_Intel]

We're sorry for the inconvenience Jung. You seem to be suffering similar symptoms as in the earlier post and a variant of the earlier assert.

You are already using the most current IDB version from the 11.1.067 (Mac OS) update, so I do not have any relief to offer at the moment. Another 11.1 update will be available in a few days that contains IDB Build [1.2097.2.295] but there is no information suggesting it will address the particular assert you suffered.

I will notify the IDB Development team about this assert and post when I have more information.

(Internal tracking id: DPD200141305)

[jungwukh]

Dear Kevin,

Thank you very much.

I will look forward to using the new version.

Best,

Jung

Quoting - Kevin Davis (Intel)

We're sorry for the inconvenience Jung. You seem to be suffering similar symptoms as in the earlier post and a variant of the earlier assert.

You are already using the most current IDB version from the 11.1.067 (Mac OS) update, so I do not have any relief to offer at the moment. Another 11.1 update will be available in a few days that contains IDB Build [1.2097.2.295] but there is no information suggesting it will address the particular assert you suffered.

I will notify the IDB Development team about this assert and post when I have more information.

(Internal tracking id: DPD200141305)

[Hubert_H_Intel]

Quoting - jungwukh

Jung,

The Inte C++ Compiler 11.1 Update 3 for MacOS X (package ID 11.1.076) is released and available for download from the Intel Registration Center.
However, defect DPD200141305 didn't get it into the fixes for this release.
But please download and install the update 11.1.076 anyway; there may be fixes from related defects that may have influence to the problem you reported.
Please let us know what's the result with 11.1.076. Thanks!
Hubert.