Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » eclipse debug platform: starting directly in suspend mode and connecting variable view
eclipse debug platform: starting directly in suspend mode and connecting variable view [message #336657] Fri, 26 June 2009 09:45
Ralf Buschermoehle is currently offline Ralf BuschermoehleFriend
Messages: 81
Registered: July 2009
Member
Hello,

I would like to connect our interpreter to the debug platform - but the
example http://www.eclipse.org/articles/Article-Debugger/how-to.html is
way to elaborated for our purpose (same applies to the sources).

What we have:
- Launch configuration, incl.
IDebugTarget target = new RMOFDebugTarget(launch);
launch.addDebugTarget(target);
There is no need to connect to an external vm/process - so I skipped the
process invocation parts, like
Process process = DebugPlugin.exec(commandLine, null);
IProcess p = DebugPlugin.newProcess(launch, process, "My Debugger");

2.) Some kind of Debug Model (Target, Thread, StackFrame) roughly
connected to our interpreter e.g., isTermined checks the running
interpreter ...
@Override
public boolean isTerminated() {
return !Interpreter.run;
}
.... but mainly unimplemented stubs.


What we don't have:

- Support of debug actions (resume, step, step into). isTerminated the
only action supported (more or less) correctly from the debug view. What
do I need to call/fire (initially fireCreationEvent();
fireSuspendEvent(DebugEvent.SUSPEND); is called) to tell the debug
platform that initially and directly that we are in step mode /
suspended? A simple isSuspended() returning 'true' is not called?

- Support of the views (i.e. debug view itself - current operational
frame & variables view) in terms of content (e.g., the current set of
transitions working on, the current variable scope dealing with a.s.o.)

I would like to keep it as simple as possible (in the first shot), so we
don't have an events (since we can directly access the interpreter),
threads (since only one instance can be executed in the graphical
environment at a time) and we don't need breakpoints (well there are
some in the models - but the debug environment does not need to handle
them right now).

Any help would be appreciated :)

Greetings,

Ralf
Previous Topic:Problem with Galileo
Next Topic:Problem with Eclipse ANT integration
Goto Forum:
  


Current Time: Sat Dec 20 05:12:01 GMT 2014

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

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