Re: [Dltk-dev] Breakpoint and dbgp question

[Alex Panchenko <alex@xxxxxxxxx>]

Hi,

In the current version initially breakpoints are sent from the initializeSession(IDbgpSession) method of org.eclipse.dltk.internal.debug.core.model.ScriptBreakpointManager.
The easiest way is to set breakpoint in the body of this method and look what really happens there.

After that you can debug e.g. breakpointAdded(IBreakpoint) to make sure that new breakpoints are relayed to the debugger engine.

Regards,
Alex

----- Original Message -----
From: "Christian Thillemann" <christianthillemann@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Wednesday, February 18, 2009 7:51:58 PM GMT +06:00 Almaty, Novosibirsk
Subject: Re: [Dltk-dev] Breakpoint and dbgp question




Hi again Alex, 

First of all; thank you for your swift response! 

As you wrote; all registered breakpoints should be sent to the debugging engine at the start of a new session. Our problem however, and that was actually the question in the first in the first mail (sorry for not being precise enough), is that this doesn’t happen. The debugger sends a nice init packet and the ide sends the set_feature command and so forth. We can run the thing as well, but for some reason the IDE does not send the set_breakpoint command. 

Do you have an idea about what the reason for this not happening could be? 

We also want to thank you for your response on our second question too, I think we’re gonna go for the custom DBGP commands approach. 

Cheers 

Dave & Christian 
Alex Panchenko skrev: 

Hi David & Christian,

There are two ways to send breakpoints to the debugging engine.
At the start of the new session all registered breakpoints are sent to the debugging engine.
Next org.eclipse.dltk.internal.debug.core.model.ScriptBreakpointManager instance (for each session) is registered to listen for breakpoint changes. So future breakpoint changes are relayed to the debugging engine. You can turn on the DBGP logging, so actually sent commands and responses could be monitored in the view.
You can debug what actually happens there, since it is hard to tell why it does not work for you.

If you need to pass something to the debugging engine then you basically have 2 ways: command line and socket connection (introduce custom DBGP commands and send them after session start). Just select the one that better fits your use case.

Regards,
Alex

----- Original Message -----
From: "Christian Thillemann" <christianthillemann@xxxxxxxxx> To: dltk-dev@xxxxxxxxxxx Sent: Tuesday, February 17, 2009 9:00:01 PM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] Breakpoint and dbgp question

Hi

Sorry for disturbing you, but we really hope that you can give a little 
help to move on from a bit of a standstill…

We are two students at Aarhus University and Engineering College of 
Aarhus currently working on our master thesis in software engineering. 
As part of our thesis we are integrating VDM with Eclipse. We are 
currently trying to get the debugging features up and running. The 
project is part of the Overture initiative, for more information you can 
visit: http://www.overturetool.org/twiki/bin/view/Main/WebHome We are using the debug protocol; DBGP and the dynamic language toolkit; 
DLTK. We’ve been looking at the org.eclipse.dltk.javascript and 
org.eclipse.dltk.ruby projects and even though we sometimes could wish 
for a bit more documentation, we are steadily moving in the right direction.

The reason we write to you is to kindly ask whether you have a piece of 
advice concerning the breakpoint functionality. We can add breakpoints 
in the editor, but it seems that the IDE doesn’t send the 
*breakpoint_set* command to the debugger engine.

In other words it seems like we have only implemented the UI 
functionality to add breakpoints in the editor, but not the actual 
features to make the machinery work…

We do realize that you properly aren’t able to tell us exactly where the 
problem lies, but can you give us a hint towards what project we might 
get some inspiration from and what extensions we want to look at.


And while we at it; we have another minor question: In our dbgp server 
part we what to access all source files in the project. How are these 
files or file paths obtained in the smartest way? We considered creating 
a new XML-file with the filenames and send the path to it in the 
arguments, this however doesn't strike us as the most elegant approach...


Thanks in advance

Cheers David Møller & Christian Thillemann


_______________________________________________
dltk-dev mailing list dltk-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dltk-dev _______________________________________________
dltk-dev mailing list dltk-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dltk-dev 

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev