Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
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] Mon, 06 February 2006 02:57 Go to next message
Eclipse UserFriend
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 06:49 Go to previous messageGo to next message
Eclipse UserFriend
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 20:27 Go to previous message
Eclipse UserFriend
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:
  


Current Time: Thu Dec 26 20:24:00 GMT 2024

Powered by FUDForum. Page generated in 0.05100 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top