Home » Language IDEs » C / C++ IDE (CDT) » Cannot debug: "No executable specified"
| Cannot debug: "No executable specified" [message #65673] |
Thu, 03 April 2003 16:43  |
Eclipse User |
|
|
|
Originally posted by: dan.hoyt.usa.net
I cannot seem to get the CDT 1.0.1 debugger to load an executable.
I get the same results with any combination of Eclipse 2.0.2 or 2.1, gdb
5.1.1 or 5.2.1, GDB or Cygwin GDB in the Debug Run Configuration I created
for this debug session (Project="EclipseHello", Program="bin/hello.exe").
After seeing the post on spaces in the path, I tried setting a local
directory to the Windows short names instead of the Default Working
Directory, but the results were the same.
I'm confused, because I can bring up "gdb bin/hello.exe" from the command
line, and the program gets loaded properly, including finding my source at
../src/hello.cpp. What am I doing wrong here?
Using the sample "HelloWorld" program on the CDT site, I get the error
window:
"Unable to set temporary breakpoint in main. Reason: No symbol table is
loaded. Use the "file" command. Continue?"
After I click on "Yes", I get a follow-up error window:
"The execution of program is suspended because of error."
Clicking the "Details>>" button reveals:
"No executable specified, use 'target exec'."
Clicking the "Show Debugger Console on Target Selection" reveals:
info threads
No stack.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
No executable specified, use `target exec'.
info threads
No stack.
No registers.
info threads
No stack.
info threads
No stack.
The .log file has:
!ENTRY org.eclipse.cdt.debug.core 4 1000 Apr 03, 2003 14:27:28.375
!MESSAGE Internal error logged from CDI Debug:
!STACK 0
org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException: No symbol table is
loaded. Use the "file" command.
at
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(BreakpointManager.java:438)
at
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setLi neBreakpoint(CDebugTarget.java:1596)
at
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.break pointAdded(CDebugTarget.java:633)
at
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alizeBreakpoints(CDebugTarget.java:310)
at
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alize(CDebugTarget.java:270)
at
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init >(CDebugTarget.java:256)
at org.eclipse.cdt.debug.core.CDebugModel$1.run(CDebugModel.jav a:117)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1595)
at
org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:130)
at
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(LocalCLaunchConfigurationDelegate.java:100)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:156)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:676)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialog$6.run(LaunchConfigurationsDialog.java:1232 )
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)
|
|
|
| Re: Cannot debug: "No executable specified" [message #65718 is a reply to message #65673] |
Thu, 03 April 2003 20:56  |
| Eclipse User |
|
|
|
Originally posted by: mikhailkhod.rogers.com
The CDT pass the full path of the executable to gdb as an argument. It
seems that the full path of your executable contains spaces. This bug is
fixed in the head branch.
Try to create a new project and set the location to some directory that
doesn't contain spaces.
"Dan Hoyt" <dan.hoyt@usa.net> wrote in message
news:b6i9us$q1t$1@rogue.oti.com...
> I cannot seem to get the CDT 1.0.1 debugger to load an executable.
>
> I get the same results with any combination of Eclipse 2.0.2 or 2.1, gdb
> 5.1.1 or 5.2.1, GDB or Cygwin GDB in the Debug Run Configuration I created
> for this debug session (Project="EclipseHello", Program="bin/hello.exe").
> After seeing the post on spaces in the path, I tried setting a local
> directory to the Windows short names instead of the Default Working
> Directory, but the results were the same.
>
> I'm confused, because I can bring up "gdb bin/hello.exe" from the command
> line, and the program gets loaded properly, including finding my source at
> ./src/hello.cpp. What am I doing wrong here?
>
> Using the sample "HelloWorld" program on the CDT site, I get the error
> window:
> "Unable to set temporary breakpoint in main. Reason: No symbol table is
> loaded. Use the "file" command. Continue?"
>
> After I click on "Yes", I get a follow-up error window:
> "The execution of program is suspended because of error."
>
> Clicking the "Details>>" button reveals:
> "No executable specified, use 'target exec'."
>
> Clicking the "Show Debugger Console on Target Selection" reveals:
> info threads
> No stack.
> No symbol table is loaded. Use the "file" command.
> No symbol table is loaded. Use the "file" command.
> No symbol table is loaded. Use the "file" command.
> No executable specified, use `target exec'.
>
> info threads
> No stack.
> No registers.
> info threads
> No stack.
> info threads
> No stack.
>
> The .log file has:
> !ENTRY org.eclipse.cdt.debug.core 4 1000 Apr 03, 2003 14:27:28.375
> !MESSAGE Internal error logged from CDI Debug:
> !STACK 0
> org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException: No symbol table is
> loaded. Use the "file" command.
> at
>
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(Br
eakpointManager.java:438)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setLi neBreakpoint(CDe
bugTarget.java:1596)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.break pointAdded(CDebu
gTarget.java:633)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alizeBreakpoints
(CDebugTarget.java:310)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alize(CDebugTarg
et.java:270)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init >(CDebugTarget.j
ava:256)
> at org.eclipse.cdt.debug.core.CDebugModel$1.run(CDebugModel.jav a:117)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1595)
> at
>
org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:130)
> at
>
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
alCLaunchConfigurationDelegate.java:100)
> at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
on.java:156)
> at
>
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.jav
a:676)
> at
>
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialo
g$6.run(LaunchConfigurationsDialog.java:1232)
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext
..java:101)
>
>
|
|
|
| Re: Cannot debug: "No executable specified" [message #65933 is a reply to message #65673] |
Fri, 04 April 2003 20:42 |
| Eclipse User |
|
|
|
Originally posted by: groups.asd-group.com
I had a similar problem, which went away when:
1) Just entering the EXE file name, without any directory specification
(which comes from the named project)
2) Ensuring that the makefile tells GCC to output symbol tables (eg. add
-ggdb to compile and link lines in makefile)
3) Setting \'Cygwin DBG Debugger\' in the Debug dialog box (even though
I\'m using MingW).
4) Ensuring that the MingW GDB update (to the last MingW release 2.0.0.3)
is installed.
I\'m not sure which of the above fixed it, but something did!
Hope that helps.
----------
Dan Hoyt wrote:
> I cannot seem to get the CDT 1.0.1 debugger to load an executable.
> I get the same results with any combination of Eclipse 2.0.2 or 2.1, gdb
> 5.1.1 or 5.2.1, GDB or Cygwin GDB in the Debug Run Configuration I created
> for this debug session (Project=\"EclipseHello\",
Program=\"bin/hello.exe\").
> After seeing the post on spaces in the path, I tried setting a local
> directory to the Windows short names instead of the Default Working
> Directory, but the results were the same.
> I\'m confused, because I can bring up \"gdb bin/hello.exe\" from the command
> line, and the program gets loaded properly, including finding my source at
> ../src/hello.cpp. What am I doing wrong here?
> Using the sample \"HelloWorld\" program on the CDT site, I get the error
> window:
> \"Unable to set temporary breakpoint in main. Reason: No symbol table is
> loaded. Use the \"file\" command. Continue?\"
> After I click on \"Yes\", I get a follow-up error window:
> \"The execution of program is suspended because of error.\"
> Clicking the \"Details>>\" button reveals:
> \"No executable specified, use \'target exec\'.\"
> Clicking the \"Show Debugger Console on Target Selection\" reveals:
> info threads
> No stack.
> No symbol table is loaded. Use the \"file\" command.
> No symbol table is loaded. Use the \"file\" command.
> No symbol table is loaded. Use the \"file\" command.
> No executable specified, use `target exec\'.
> info threads
> No stack.
> No registers.
> info threads
> No stack.
> info threads
> No stack.
> The .log file has:
> !ENTRY org.eclipse.cdt.debug.core 4 1000 Apr 03, 2003 14:27:28.375
> !MESSAGE Internal error logged from CDI Debug:
> !STACK 0
> org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException: No symbol table is
> loaded. Use the \"file\" command.
> at
>
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(BreakpointManager.java:438)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setLi neBreakpoint(CDebugTarget.java:1596)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.break pointAdded(CDebugTarget.java:633)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alizeBreakpoints(CDebugTarget.java:310)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alize(CDebugTarget.java:270)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init >(CDebugTarget.java:256)
> at org.eclipse.cdt.debug.core.CDebugModel$1.run(CDebugModel.jav a:117)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1595)
> at
> org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:130)
> at
>
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(LocalCLaunchConfigurationDelegate.java:100)
> at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:156)
> at
>
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:676)
> at
>
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialog$6.run(LaunchConfigurationsDialog.java:1232 )
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)
|
|
|
| Re: Cannot debug: "No executable specified" [message #66295 is a reply to message #65673] |
Tue, 08 April 2003 14:18 |
| Eclipse User |
|
|
|
Originally posted by: dan.hoyt.usa.net
Thanks for the suggestions. I was able to work around this by going back
and recreating the project in the same location, but modifying the
Location to use the Windows shortnames instead (e.g.
C:\Docume~\MyName~1\MyDocu~1\Projects\... instead of C:\Documents and
Settings\My Name\My Documents\Projects\...).
Looking forward to the next CDT GA release!
-Dan Hoyt
Dan Hoyt wrote:
> I cannot seem to get the CDT 1.0.1 debugger to load an executable.
> I get the same results with any combination of Eclipse 2.0.2 or 2.1, gdb
> 5.1.1 or 5.2.1, GDB or Cygwin GDB in the Debug Run Configuration I created
> for this debug session (Project="EclipseHello", Program="bin/hello.exe").
> After seeing the post on spaces in the path, I tried setting a local
> directory to the Windows short names instead of the Default Working
> Directory, but the results were the same.
> I'm confused, because I can bring up "gdb bin/hello.exe" from the command
> line, and the program gets loaded properly, including finding my source at
> ../src/hello.cpp. What am I doing wrong here?
> Using the sample "HelloWorld" program on the CDT site, I get the error
> window:
> "Unable to set temporary breakpoint in main. Reason: No symbol table is
> loaded. Use the "file" command. Continue?"
> After I click on "Yes", I get a follow-up error window:
> "The execution of program is suspended because of error."
> Clicking the "Details>>" button reveals:
> "No executable specified, use 'target exec'."
> Clicking the "Show Debugger Console on Target Selection" reveals:
> info threads
> No stack.
> No symbol table is loaded. Use the "file" command.
> No symbol table is loaded. Use the "file" command.
> No symbol table is loaded. Use the "file" command.
> No executable specified, use `target exec'.
> info threads
> No stack.
> No registers.
> info threads
> No stack.
> info threads
> No stack.
> The .log file has:
> !ENTRY org.eclipse.cdt.debug.core 4 1000 Apr 03, 2003 14:27:28.375
> !MESSAGE Internal error logged from CDI Debug:
> !STACK 0
> org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException: No symbol table is
> loaded. Use the "file" command.
> at
>
org.eclipse.cdt.debug.mi.core.cdi.BreakpointManager.setLocat ionBreakpoint(BreakpointManager.java:438)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.setLi neBreakpoint(CDebugTarget.java:1596)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.break pointAdded(CDebugTarget.java:633)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alizeBreakpoints(CDebugTarget.java:310)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.initi alize(CDebugTarget.java:270)
> at
>
org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init >(CDebugTarget.java:256)
> at org.eclipse.cdt.debug.core.CDebugModel$1.run(CDebugModel.jav a:117)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1595)
> at
> org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebug Model.java:130)
> at
>
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(LocalCLaunchConfigurationDelegate.java:100)
> at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:156)
> at
>
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:676)
> at
>
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialog$6.run(LaunchConfigurationsDialog.java:1232 )
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:101)
|
|
|
Goto Forum:
Current Time: Fri May 23 15:22:57 EDT 2025
Powered by FUDForum. Page generated in 0.02911 seconds |
Home