topic Re: even worse in Intel® Fortran Compiler

idb : Unrecognized binary file format

bpichon — Wed, 22 Jun 2005 23:04:38 GMT

I have seen some old posts concerning this problem that should be fixed with the newer version of idb (post dated 26 apr 2005 from gasaladi)

BUT

=======================================================

Dear Fortran

1) I compile the test program

--------------------------------------

(see attached file whichpresent a trivial

error on line8 and also 18)

*** with the32 bit version of ifort (fc)

and

***with the EM64T version of ifort (fce) :

/opt/intel/fc/9.0/bin/ifort -g -CB -traceback -o bound-fc.exe bound.f90

/opt/intel/fce/9.0/bin/ifort -g -CB -traceback -o bound-fce.exe bound.f90

(see also attached files "fc.log" and "fce.log" that contain the result

of compilationand link with verbose options namely: "-v -V" )

2) I verify that it isOK :

-----------------------------

*** file bound-fc.exe
bound-fc.exe: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),

for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped

*** file bound-fce.exe
bound-fce.exe: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV),

for GNU/Linux 2.4.1, dynamically linked (uses shared libs), not stripped

3) I try to debug this program :

---------------------------------------

with idg (32 bits version),it is OK :

*** idb bound-fc.exe
Linux Application Debugger for Intel EM64T-based applications,

Version 9.0-10, Build 20050413
------------------
object file name: bound-fc.exe
Reading symbolic information from /home1/pichon/DEBUG/bound-fc.exe...done
(idb) quit

*** idb-e bound-fc.exe
Linux Application Debugger for Intel EM64T-based applications,

Version 9.0-10, Build 20050413
------------------
object file name: bound-fc.exe
Reading symbolic information from /home1/pichon/DEBUG/bound-fc.exe...done
(idb) quit

BUT WITH THE EM64T version, it fails !!!!

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

(We have AMD-Opteron processors and thus we are interested by the

EM64T versionsofour programs .....)

***idb-e bound-fce.exe
Linux Application Debugger for Intel EM64T-based applications,

Version 9.0-10, Build 20050413
------------------
object file name: bound-fce.exe
Unrecognized binary file format for file /home1/pichon/DEBUG/bound-fce.exe
Could not start process for bound-fce.exe
No image loaded ... Recovering ...
(idb) quit

THE SAME with the C compiler :

Intel C Compiler for Intel EM64T-based applications, Version 9.0

Build 20050430 Package ID: l_cc_p_9.0.021

Question : How to fix that (we think that we have the latest version of

^^^^^^^^^^^^^^ ifort, idb, icc)

Yours sincerely,

Bernard PICHON
--
Dr. Bernard PICHON
Dpartement Cassiope (UMR 6202 du CNRS)
Observatoire de la Cte d'Azur (OCA) Nice
BP 4229 06304 Nice Cedex 04
Telephone : 04 92 00 31 83
Telecopie : 04 92 00 31 21
Sur la toile : http://www.obs-nice.fr/pichon/

Re: idb : Unrecognized binary file format

Steven_L_Intel1 — Wed, 22 Jun 2005 23:50:17 GMT

I would recommend that you submit an issue to Intel Premier Support about this.

even worse

tgeenenat — Tue, 27 Sep 2005 16:34:59 GMT

It seems to be even worse.
when compiled with -g -traceback i still get
forrtl: severe (408): fort: (3): Subscript #1 of the array TRACER_STATUS has value -9998which is less than the lower bound of 1

Image PC Routine Line Source
test_3d 00000000004BE50E Unknown Unknown Unknown
test_3d 00000000004BBED2 Unknown Unknown Unknown
libifcore.so.5 00002AAAAE6D2234 Unknown Unknown Unknown

and when using gdb I get
forrtl: severe (408): fort: (3): Subscript #1 of the array TRACER_STATUS has value -9998which is less than the lower bound of 1

Image PC Routine Line Source
test_3d 00000000004BE50E Unknown Unknown Unknown
test_3d 00000000004BBED2 Unknown Unknown Unknown
libifcore.so.5 00002AAAAE6D2234 Unknown Unknown Unknown

Program exited with code 0230.
(gdb) where
No stack.

i run version fort (IFORT) 9.0 20050430
on an amd64
ldd /opt/intel/fortran90/bin/fortcom
linux-gate.so.1 => (0xffffe000)
libm.so.6 => /lib32/libm.so.6 (0x5557c000)
libstdc++.so.5 => /emul/linux/x86/usr/lib32/libstdc++.so.5 (0x5559f000)
libgcc_s.so.1 => /emul/linux/x86/usr/lib32/libgcc_s.so.1 (0x55652000)
libc.so.6 => /lib32/libc.so.6 (0x5565b000)
/lib/ld-linux.so.2 (0x55555000)

will this be resolved in the next version?
not being able to debug is not quit an option for me

cheers
Thomas Geenen

Re: even worse

tgeenenat — Tue, 27 Sep 2005 16:39:43 GMT

this was supposed to be a reply/extension to
http://softwareforums.intel.com/ids/board/message?board.id=11&message.id=2657

cheers
Thomas

Re: even worse

TimP — Tue, 27 Sep 2005 19:58:33 GMT

I know this forum has become more difficult to use, but please, when the subject doesn't fill in correctly on your reply, discard it, log in to the forum again, and reply to the message you intend.

Your original message indicates that you were using compiler 9.0.021. Both the compiler and the idb debugger are much improved in 9.0.027. Note that 'idb -gdb' accepts gdb style commands.

Re: even worse

Steven_L_Intel1 — Tue, 27 Sep 2005 21:44:50 GMT

I moved the reply, now that I knew where it went.

The forum has an issue that if you reply while not logged in, after you log in it goes to a new topic page (but with the subject filled in making you think it is a reply) instead of as a reply. I have already reported this.

Re: even worse

tgeenenat — Wed, 28 Sep 2005 18:17:11 GMT

thanks for fixing the thread
I looked for the 9.0.027 version of ifort but could not find it. only the 21 version.
ftp://download.intel.com/software/products/compilers/downloads/eval/preview
could you provide me with the link for the newest ifort compiler?
you mentioned idb-gdb does this mean that idb will work with ddd i had some troubles in the past with the combination idb ddd

cheers
Thomas

Re: even worse

Steven_L_Intel1 — Wed, 28 Sep 2005 20:19:06 GMT

The 027 compiler is currently available for customers with full support. The most recent compiler for Limited Support customers is 026. Both are in Intel Premier Support File Downloads.

My guess is that you have not registered your serial number and are just looking at the FTP area for initial downloads. This does not get updated on a regular basis. Please register your serial number and then you'll get access to Premier Support.