|
|
|
Re: Remote Debugging [message #496473 is a reply to message #496214] |
Tue, 10 November 2009 09:04 |
Alex Panchenko Messages: 342 Registered: July 2009 |
Senior Member |
|
|
Hi Suprit,
This issue should be fixed in
http://download.eclipse.org/technology/dltk/downloads/drops/ R2.0/I-I200911091822-200911091822/
Could you please check if it works for you.
Regards,
Alex
Alex Panchenko wrote:
> Hi Suprit,
>
> I will fix tonight.
> And the next stable version (M3) is scheduled on this week.
>
> Regards,
> Alex
>
>
> suprit wrote:
>> Hi,
>> I have debugged the above mentioned issue and found that in method
>> "acceptLaunch" of source "org.eclipse.dltk.debug.ui.DebugConsoleManager"
>> , they have added a check "launch.getProcesses().length != 0" as shown
>> below :
>> (in dltk 2.0)
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> protected boolean acceptLaunch(ILaunch launch) {
>> ...
>>
>> // FIXME test for remote session? return
>> launch.getProcesses().length != 0 &&
>> DLTKDebugLaunchConstants.isDebugConsole(launch);
>> }
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> But in Remote debugging,the IDE doesn't launch any process and starts
>> listening on a pre-defined port,hence method "acceptLaunch" always
>> returns "false" to "launchesChanged(ILaunch[] launches)" method because
>> of which no console is added in the target.Hence no output is shown in
>> the console.
>>
>> In dltk 1.0,it was as follows :
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> protected boolean acceptLaunch(ILaunch launch) {
>> ....
>>
>> return DLTKDebugLaunchConstants.isDebugConsole(launch);
>> }
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Can you provide the fix in the stable version of DLTK 2.0?
>>
>> regards,
>> Suprit
|
|
|
Powered by
FUDForum. Page generated in 0.03962 seconds