Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 158312 - [remotecdt] Remote CDT Launch fails with dstore connections
Summary: [remotecdt] Remote CDT Launch fails with dstore connections
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 161773
Blocks:
  Show dependency tree
 
Reported: 2006-09-22 10:44 EDT by Martin Oberhuber CLA
Modified: 2008-08-13 13:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2006-09-22 10:44:55 EDT 
Remote CDT Launch fails with dstore connections.
Ssh is OK.

A particular problem turns up when the dstore connection is selected, but not connected at the time the Launch is initiated.
While the Remote CDT Launchis ongoing, the Remote Shell shows Dstore frames but not the output from the remote side.

-----------Enter bugs above this line-----------
RSE 1.0 Testing round 1
installation : Eclipse M20060629-1905 platform-3.2, cdt-sdk-3.1.0
RSE install  : download RSE-runtime-core, runtime-dstore, runtime-remotecdt
java.runtime : Sun 1.5.0_07-b03
os.name:     : Windows XP 5.1, Service Pack 1
------------------------------------------------
systemtype   : Linux-dstore
targetos     : Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
targetvm     : Sun 1.4.2_12-b03
--------------------------------------
Comment 1 Martin Oberhuber CLA 2006-09-22 10:45:47 EDT 
Ewa, can you look at this?
Comment 2 Martin Oberhuber CLA 2006-11-02 08:02:52 EST 
According to Norbert Ploett, this works with 1.0RC3 thanks to the fix in bug 161773.
Comment 3 Martin Oberhuber CLA 2008-08-13 13:08:13 EDT 
[target cleanup] 1.0 RC3 was the original target milestone for this bug