debug engine overview [message #6384] |
Sun, 10 June 2007 18:52  |
Eclipse User |
|
|
|
could someone provide a quick overview in how the debugging
engine/framework works.
i see that there is no longer spawned via launch configuration
delegates, so i'm trying to understand how that entire process works. i
know that the debugger attaches to the ide, instead of the other way
around.
leaving aside remote debugging, if i wanted to debug a program locally,
wouldn't i still want the ability to have a debug launch shortcut that
started up the interpreter process from inside the ide?
thx!
|
|
|
|
|
|
|
|
Re: debug engine overview [message #6570 is a reply to message #6552] |
Tue, 19 June 2007 11:22  |
Eclipse User |
|
|
|
On 2007-06-19 09:18:14 -0400, Dmitriy Kovalev <kds@xored.com> said:
> Hello Jae,
>
> If I understand correctly, you derived your class from
> DebuggingEngineRunner and overrode method 'run' to handle stdout/stderr
> of the Process that you launched. I think we should extend our core
> classes to allow handle situations like you have. It would be very
> helpful if you can send your sources related to interpreter launching
> to kds@xored.com In this situation I can investigate your code and
> implement good general solution.
that is correct.
in this situation, i only need to hook into the Process object to
determine why the program couldn't be started using the debugging
engine.
let me get things cleaned up a bit, and i'll create a patch.
--
-jae
|
|
|
Powered by
FUDForum. Page generated in 0.07251 seconds