not able to add debug info in to the build process

[aditya_achlerkar]

Hi,

I am trying to build a project which contains some fortran files and some obj files (c codes compiled into obj files). These obj files are compiled using cygwin with stuffing debug info. I am including these files into the source category of the project in visual develepor studio for compaq fortan.

When I try to build the project and debug it it gives me message stating that "somename.exe" dosen't have debug info, and it disables the breakpoints.

I tried using all options debugger has. I found out that when I use debug info check box, and select Microsoft format from the tab Project->Properties->Link, the compiler gives error stating that one of the obj's whichI included are corrupted and recompile it. But if I don't use this option (Microsoft Fomat) then the error goes on but the project won't go into debug mode.

Can anybody tell me what is actually happening and what needs to be done regarding this. ANy immediate help is very much appriciated and needed.

[TimP]

GNU compiler debugging isn't compatible with Microsoft debugging. Microsoft intends it that way.
You may be able to debug to a limited extent, using the cygwin debugging tools, but only GNU style debug symbols will permit source level debugging.

[aditya_achlerkar]

Hi,

thanks for the information, but I am also trying to make it debuggable on Compaq Visual fortron compiler, but still not able to.

I wrote previously :-> tried using all options debugger has. I found out that when I use debug info check box, and select Microsoft format from the tab Project->Properties->Link, the compiler gives error stating that one of the obj's whichI included are corrupted and recompile it. But if I don't use this option (Microsoft Fomat) then the error goes on but the project won't go into debug mode.

Can you tell me more about it why this is happening? I incorporated debug info in the object files thatI am using still this problem is occuring.

Aditya

[TimP]

When you use the Microsoft link with debug on, it will warn you about .obj files where it doesn't accept the debug information. That warning is expected when the .obj is built with gcc. If link is successful, debugging may still be possible when control doesn't pass through the rejected .obj.

[aditya_achlerkar]

Well, I am not suing gcc but using MD (microsoft debugger for compiling and debugging) thru cygwin. I have visual studio .net and compaq fortron installed on my machine. I tried it in another machine (which is core-loaded) and it worked fine there, does that mean, the problem is in Visual Studio compiler I am having (as it may not be up to date as mine is non core-loaded machine)?