| CDT 4.0.0 M5 Variables window kills debugging -- ideas? [message #188196] |
Wed, 28 March 2007 03:13  |
Eclipse User |
|
|
|
Originally posted by: noreally.notaserver.com
Folks:
Anyone have any clue whether this is work-around-able?
Eclipse 3.3M5eh with CDT 4.0.0 M5 linux (Centos 4)
This is a "Standard Make" project.
I can single step through my project, but if I open the Variables window, on
the next step the debugger appears to hang (though I can terminate the app
with the terminate button).
In the console window I get the error output shown below.
FWIW, if I terminate the app, close the Variables window, and then start
debugging again, no problem.
Graham
----------------------------------------------------
[graham@gwlinux eclipse_3.3M5eh]$ ./eclipse_launch.bash
Exception in thread "MI Event Thread" java.lang.StackOverflowError
at java.util.Hashtable.get(Unknown Source)
at java.util.Properties.getProperty(Unknown Source)
at java.util.Properties.getProperty(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at
org.eclipse.cdt.debug.mi.core.output.MIConst.isoC(MIConst.ja va:94)
at
org.eclipse.cdt.debug.mi.core.output.MIConst.getString(MICon st.java:50)
at
org.eclipse.cdt.debug.mi.core.output.MIStreamRecord.getStrin g(MIStreamRecord.java:29)
at
org.eclipse.cdt.debug.mi.core.command.Command.throwMIExcepti on(Command.java:95)
at
org.eclipse.cdt.debug.mi.core.command.MIVarCreate.getMIInfo( MIVarCreate.java:72)
at
org.eclipse.cdt.debug.mi.core.command.MIVarCreate.getMIVarCr eateInfo(MIVarCreate.java:63)
at
org.eclipse.cdt.debug.mi.core.cdi.model.Variable.getMIVar(Va riable.java:131)
at
org.eclipse.cdt.debug.mi.core.cdi.VariableManager.update(Var iableManager.java:662)
at
org.eclipse.cdt.debug.mi.core.cdi.VariableManager.update(Var iableManager.java:682)
[... 100's of repetitions of this last line...]
|
|
|
|
|
| Re: CDT 4.0.0 M5 Variables window kills debugging -- ideas? [message #188418 is a reply to message #188386] |
Thu, 29 March 2007 04:52  |
| Eclipse User |
|
|
|
Originally posted by: Jens.Seidel.imkf.tu-freiberg.de
Derek Morris wrote:
> Are you aware that 4.0M5 is not released? It primarily aimed at (very)
> early adopters who are developing new features/plugins for 4.0. As such,
> it is missing features, and it is known to be buggy (debug is one area
> that is in flux). This is to be expected as it is not for release until
> June this year. If you want a stable release, you should be using Eclipse
> 3.2.2 and CDT 3.1.2.
It is already well suited for testing and developers reply to and fix bugs
very fast.
> However, I am sure the developers would be interested in a bug report.
> Please report at: https://bugs.eclipse.org/bugs/
I noticed the same problem (but my initial posting to your one got lost).
Once a variable which is optimized away is selected the gdb console prints
many duplicated messages. Please post here your bug number so that I can
add myself to CC:
Jens
|
|
|
Powered by
FUDForum. Page generated in 0.13161 seconds
Home