idb debugger and snow leopard

[mariano_vazquez]

hi all,

idb debugger in my mac with snow leopard is not working at all.. i attach a code which is an extract of a longer one. i have isolated the problem in these lines.

i compile the code using this:

ifort -g -save-temps -o testillo test.f90
 

and i run under debugger doing "idb testillo". in the program test.f90 the first executable line is a "stop". so once

i enter the debugger i plainly do "run" and this is what i get:

MyMac: ~/Programs/idb-issues #93 > idb testillo
Intel Debugger for applications running on Intel 64, Version 11.1, Build [1.2097.2.319]
------------------
object file name: testillo
Reading symbols from /Users/mariano/Programs/idb-issues/testillo...done.
(idb) run
Starting program: /Users/mariano/Programs/idb-issues/testillo
iidb(26328) malloc: *** error for object 0x50202b5300000000: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

Intel Debugger for applications running on Intel 64, Version 11.1 caught signal "Abort trap" (6).
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.

terminate called after throwing an instance of 'FatalError'
Abort
MyMac: ~/Programs/idb-issues #94 > ls
 

some hints:

System Version: Mac OS X 10.6.2 (10C540)
Kernel Version: Darwin 10.2.0

xcode is: 3.2.1 (1613)

ifort (IFORT) 11.1 20091130

Intel Debugger for applications running on Intel 64, Version 11.1, Build [1.2097.2.319]

ifort was installed AFTER i installed xcode 3.2.1

for very simple codes, idb seems to work fine... but not for the normal use we debug.

i had a leopard mac, with ifort and idb and everything worked reasonably well... but since i move to snow leopard and updated my ifort and idb, debugger ceased to work well.

any help???

[Stephen_D_Intel]

Hi Mariano,

Thank you for the test case. I can reproduce the problem with idb on snow leopard using the version 11.1.080 idb. gdb handles the program successfully to we can assume that the compiler is generating valid debug information.

I will open a problem report on this but I don't have any workarounds to suggest at this time except to use gdb.

Regards,
Steve D.
Intel Developer Support

[Stephen_D_Intel]

Hi Mariano,

A problem report is already open on this so I've associated this forum posting with it.

The problem report number is DPD200083228.

Regards,
Steve D.
Intel Developer Support

[Ron_Green]

this bug was fixed some time ago.  

Since idb is deprecated, 'gdb-ia' should be used for debugging on Mac OS X

ron