Eclipse Community Forums: C / C++ IDE (CDT) » Debugger fails to debug a simple "hello world" program.

Home » Language IDEs » C / C++ IDE (CDT) » Debugger fails to debug a simple "hello world" program.

Debugger fails to debug a simple "hello world" program. [message #208735]

Mon, 28 January 2008 17:57

Eclipse User

From time to time I have mysterious problems with the debugger. Usually
deleting the project and rebuilding it from scratch fixes it. However
currently it will not debug a simple hello world program. I've deleted
the workspace, and the .project file. It still says:

Error stopping at main.
Target request failed: Target is not responding (timed out).

I'm running on linux. I tried the "verbose" option for gdb, but it
seems to print most of the output on the same line rendering it
unreadable. (prints over itself many times).

If only the simple things would work...
wcn

Re: Debugger fails to debug a simple "hello world" program. [message #208753 is a reply to message #208735]

Mon, 28 January 2008 18:23

Eclipse User

I cleaned up my environment (script I use to start eclipse so it can
build via my build files...) and now it works. What I'd really like is
a way to trace the commands used to start the debugger and interact with
it so I can "see" whats going on when it doesn't work.
wcn

Wendell Nichols wrote:
> From time to time I have mysterious problems with the debugger. Usually
> deleting the project and rebuilding it from scratch fixes it. However
> currently it will not debug a simple hello world program. I've deleted
> the workspace, and the .project file. It still says:
>
> Error stopping at main.
> Target request failed: Target is not responding (timed out).
>
>
> I'm running on linux. I tried the "verbose" option for gdb, but it
> seems to print most of the output on the same line rendering it
> unreadable. (prints over itself many times).
>
> If only the simple things would work...
> wcn

Re: Debugger fails to debug a simple "hello world" program. [message #208828 is a reply to message #208753]

Wed, 30 January 2008 03:06

Eclipse User

Wendell Nichols wrote:

> What I'd really like is
> a way to trace the commands used to start the debugger and interact with
> it so I can "see" whats going on when it doesn't work.
> wcn
Go to the tab "Debugger" in the debug configuration of your application
and check "Verbose console mode". You should see then the commands send to
the debugger.

Axel

Previous Topic:	working directory for .bat files
Next Topic:	preproccesor define in header file missing when header file included

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 23:22:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter