Re: [photran] Problem trying to debug

[DEVEL Michel <Michel.Devel@xxxxxxxx>]

Title: sincerely_yours.txt

Le 30/03/2010 16:03, DEVEL Michel a écrit :

Le 30/03/2010 15:32, Fernando Molina a écrit :

Hello Michel:

The versions are:
gcc-x64 4.4.3 (equation.com)
Eclipse IDE for C/C++ Developers Build id: 20100218-1602 (as in about box)
Eclipse Platform 3.5.2.M20100211-1343 (as in installation details)
EPP CPP Feature 1.2.2.20100209-1511 (as in installation details)
Photran End-User Runtime 5.0.1.201002011019 (as in installation details)
Rephraser Engine End-User Runtime 1.0.1.201002011019 (as in installation
details)

Hope that this is what you requested
  

Yes except for CDT version that is lacking but probably 6.0.2

However, I am a bit surprised that some things work because I thought the Win64 version would require the CDT version for Helios (eclipse 3.6 which is still currently in beta state) and not Galileo (eclipse 3.5.2).
By the way, If it works, I suppose you also have the 64bits SUN Java VM and not the 32 bits one ?

I gave a new try at that, using the same version as you (Galileo, CDT 6.0.2, PTP 3.0.1, GCC 4.4.3 from equation.com with gfortran, make and gdb)
When I tried to debug, the executable was recognized (!) and began to launch in an external console (?!?) and I got (with the standard gdb as command for "GDB debugger")

Internal error logged from CDI Debug:
 
org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException: No registers.[No registers.]
at org.eclipse.cdt.debug.mi.core.cdi.RegisterManager.getRegisterDescriptors(RegisterManager.java:195)
at org.eclipse.cdt.debug.mi.core.cdi.RegisterManager.getRegisterDescriptors(RegisterManager.java:173)
at org.eclipse.cdt.debug.mi.core.cdi.model.RegisterGroup.getRegisterDescriptors(RegisterGroup.java:42)
at org.eclipse.cdt.debug.internal.core.CRegisterManager.initialize(CRegisterManager.java:127)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initializeRegisters(CDebugTarget.java:356)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initialize(CDebugTarget.java:287)
at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init>(CDebugTarget.java:275)
at org.eclipse.cdt.debug.core.CDIDebugModel$1.run(CDIDebugModel.java:100)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
at org.eclipse.cdt.debug.core.CDIDebugModel.newDebugTarget(CDIDebugModel.java:105)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSession(LocalCDILaunchDelegate.java:162)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(LocalCDILaunchDelegate.java:112)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaunchDelegate.java:72)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

--

Sincerely yours,

Michel DEVEL