[news.eclipse.tools.cdt] Re: CDT Debugging

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

Did you compile your executable with '-g' option?

"Erwin" <erwin.de.ley@xxxxxxxx> wrote in message
news:aveclq$phl$1@xxxxxxxxxxxxxxxx
> Hi,
>
> I am using CDT 1.0.1 org.eclipse.cdt-200212181146-win32_1.0.1.bin.dist.zip
> in combination with eclipse 2.1 (eclipse-SDK-N20021115-win32.zip) on
> Win2K, which is not an officially supported combination. I use
> cygwin-1.3.18-1 with gcc-3.2-3 and gdb-20021218-1.
>
> Editing and building works fine (after changing the build command in the
> C-project-properties screen to something like
> "C:\ProgramFiles\cygwin\bin\make.exe -f makefile").
>
> Plain execution also works fine, even when referring to an executable in a
> bin folder of the C project (e.g. putting "bin/dbc_ecs.exe" in the C/C++
> application field of the "main" tab in the run configuration), and even
> using a non-default working directory (e.g. referring to the bin project
> sub-folder in the workspace).
>
> The only thing I can't manage to get working is debugging, and apparently
> many users have this same problem, also when using eclipse 2.0.x. I get
> the same behaviour as mentioned in previous postings:
> - when using the default debug settings:
>     cygwin GDB Debugger;
>     Run program in debugger
>     Stop at main() in startup
>     MI debugger: gdb
>     Load shared library ... NOT checked
>   => result is alert :
>       "Unable to set temporary breakpoint in main.
>       Reason: No symbol table is loaded. Use the "file" command.
>       Continue?"
>
> Log file info:
> !SESSION Jan 07, 2003 12:20:38.387
> ---------------------------------------------
> java.version=1.3.1_05
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
> Command-line arguments: -os win32 -ws win32 -arch x86 -install
> file:C:/ProgramFiles/eclipse/
> !ENTRY org.eclipse.debug.ui 4 120 Jan 07, 2003 12:20:38.387
> !MESSAGE Error logged from Debug UI:
> !STACK 1
> org.eclipse.debug.core.DebugException: No symbol table is loaded.  Use the
> "file" command.
> at org.eclipse.cdt.debug.core.CDebugModel.stopInMain(CDebugModel.java:468)
> at
>
org.eclipse.cdt.debug.core.CDebugModel.newDebugTarget(CDebugModel.java:142)
> at
>
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:101)
> at
>
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:144)
> at
>
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$11.run(LaunchConfigurationDialog.java:2283)
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:95)
> !ENTRY org.eclipse.cdt.debug.core 0 5010 Jan 07, 2003 12:20:38.417
> !MESSAGE No symbol table is loaded.  Use the "file" command.
>
> - when trying the commands specified by Mikhael below straight in cygwin,
> I get the same response as Michael (see below).
>
> HEEELP!
>
> Erwin.
>
> Related postings:
>
> Subject: Re: problem with step over debugging
> From: bangham@xxxxxxxxxxx (Michael)
> Newsgroups: eclipse.tools.cdt
> Organization: EclipseCorner
> Date: Jan 02 2003 19:20:43
>
> The response is:
> &"Not symbol table is loaded. Use the \"file\" command. \n"
>
>
> "Mikhail Khodjaiants" <mikhailk@xxxxxxx> wrote in message
> news:av27gu$rob$1@xxxxxxxxxxxxxxxx
> > Please, try this:
> > 1. start gdb with '-i mi' option
> > 2. type '-gdb-set auto-solib-add off' and press Enter
> >
>
>
>