| Re: [ptp-user] Unresolved breakpoints |
So if you debug this program from the command line using idb, set a breakpoint, run the code, it stops at the breakpoint., ^ n GUI IDB cannot stop at a breakpoint too, I’m out of work now and shall try command line idb on Monday but if you debug this program using a C/C++ Application from Eclipse, set a breakpoint at the same location, run the code, you see an error? Is that correct? n I tried also GDB and GCC, the same thing, it cannot stop at breakpoint too How are you configuring Eclipse to use idb? n I used standard debugger in configuration, and then in debug window I choose intel debugger from the dropdown menu, all settings are default settings Where are you seeing the "Unresolved breakpoints" message? n At the place where the breakpoint (blue point) appears, I have a triangle with an exclamation sign inside and pop-up menu Unresolved breakpoint. And all the line is underlined by an orange color. If I use the option ‘stop at main’ in the debugger window, the program is stopped and I can continue line by line (F5, F6, F7) and go to this breakpoint without any problem. But F8 (Resume) skips all breakpoints. Regards, Vitaliy On Oct 21, 2011, at 10:24 AM, Vitaliy FEOKTISTOV wrote: Hi Greg, all projects are local I created one C makefile project with intel exe toolchain, and 3 intel fortran static lib makefiles projects with intel fortran toolchain. thus all projects are makefile projects with the following compilation options 1. FORT = ifort -g3 -O0 -fpp -threads -traceback -w -C -c 2. C = icc -g3 -O0 -fpp -traceback -w -C -c 3. LINKER = ifort -static -nofor_main -o I tried separately C/C++ and Fortran local applications, no problem with debugging. with the real project I could localise that the problem is where C programm calls Fortran subroutine passing large arrays into it. Vitaliy On Fri, Oct 21, 2011 at 4:06 PM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote: Hi Vitaliy,
> _______________________________________________ _______________________________________________ |