2010-07-25 25 views
1

J'essayais d'utiliser CDT avec MinGW sous Windows 7. Il pourrait exécuter le programme sans aucune erreur; Toutefois, lorsque j'ai commencé le débogage, il a invité les messages suivants. Je n'ai aucune idée d'où était le problème. Tous les commentaires sont les bienvenus. Merci d'avance.CDT GDB Déboguer sous Windows

Failed to execute MI command:-gdb-set auto-solib-add on Error message from debugger back end: No symbol "auto" in current context.

Request for monitor: 'RequestMonitor ([email protected]1): Status ERROR: org.eclipse.cdt.dsf.gdb code=10004 Failed to execute MI command:-gdb-set auto-solib-add on Error message from debugger back end: No symbol "auto" in current context. null' resulted in an error.

Process terminate failed

Error in final launch sequence org.eclipse.core.runtime.CoreException: Failed to execute MI command: -gdb-set auto-solib-add on Error message from debugger back end: No symbol "auto" in current context.

at org.eclipse.cdt.dsf.concurrent.Sequence.abortExecution(Sequence.java:560) 

at org.eclipse.cdt.dsf.concurrent.Sequence.access$4(Sequence.java:552) 

at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleErrorOrWarning(Sequence.java:424) 

at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleFailure(RequestMonitor.java:321) 

at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:284) 

at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:246) 

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 

at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 

at java.util.concurrent.FutureTask.run(Unknown Source) 

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) 

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) 

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 

at java.lang.Thread.run(Unknown Source) 

Répondre

0

Autre version de gdb est la solution.