Eclipse Community Forums: Newcomers » Debugging C++ with Eclipse 3.1.1/CDT: Unable to view fariables

Home » Newcomers » Newcomers » Debugging C++ with Eclipse 3.1.1/CDT: Unable to view fariables

Debugging C++ with Eclipse 3.1.1/CDT: Unable to view fariables [message #135349]

Sun, 05 February 2006 21:57

Eclipse User

Originally posted by: fred_bo67.yahoo.com

I'm using a default install Eclipse 3.1.1 (which includes CDT 3.0.0) for
Fedora Core 4. I'm attempting to debug some code, however it is not able
to output the values of local variables. I get the errors:

whatis cms
Variable "cms" is not available.
Variable "dms" is not available.
Variable "dms" is not available.

In the variables view, all of the variables are unavailable. When I hover
the mouse over a local variable (for example 'i' in a loop) the console
outputs the error:

No symbol "i" in current context.

When it clearly is (I'm inside the loop).

Is this a known problem? I can view the variables using ddd (gdb) -- I
assumed that because CDT uses gdb (from my understanding) that it should
work too. What am I doing wrong?

Thanks!

Re: Debugging C++ with Eclipse 3.1.1/CDT: Unable to view variables [message #135696 is a reply to message #135349]

Tue, 07 February 2006 01:49

Eclipse User

Originally posted by: fred_bo67.yahoo.com

Previously the program was compiled with the -g flag. However I have since
tried with the -ggdb flag and I still have no luck. Can somebody shed some
light on this?

(PS: Apologies for the typo in the topic)

Re: Debugging C++ with Eclipse 3.1.1/CDT: Unable to view variables [message #140288 is a reply to message #135696]

Sat, 25 February 2006 15:27

Eclipse User

Originally posted by: jochen.wuttke.gmx.de.invalid

Aaron wrote:
> Previously the program was compiled with the -g flag. However I have since
> tried with the -ggdb flag and I still have no luck. Can somebody shed some
> light on this?
>
> (PS: Apologies for the typo in the topic)
>

I had a similar problem.
Go to the advanced debugger settings in the "Debug..." -> your config dialog.
Chose any protocol ( mi1, mi2, or mi3 ). Run the debug and see if the
variables are there. In my case they were, and I could even switch back to the
default setting of mi afterwards and it still worked. Seems there is a glitch
somewhere.

Previous Topic:	I cannot see TCP/IP Monitor in Preferences?
Next Topic:	eclipse startup problem

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Aug 30 23:07:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter