Bugzilla – Full Text Bug Listing
| Summary: | executable path is "sticky" | ||
|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Albert L. Rossi <arossi> |
| Component: | Launch | Assignee: | Greg Watson <g.watson> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
I think this is now fixed. The problem was that the wd was being set when validating launch attributes. This causes the "Use default working directory" check box to be unselected and the wd entered in the Directory field. If the connection is subsequently changed, the wrong wd will be used. NOTE: a wd is now no longer always available in the launch attributes. Launchees will need to determine the wd if the default is selected (normally the location of the executable). Please verify everything is still working ok. |
Steps to reproduce the bug: 1. Start with a clean resource manager. Create a generic resource manager. 2. Initialize connection to remote host A where you have a remote project A 3. Start the manager. 4. Create a new parallel application (launch tab) 5. Go to the application tab and choose remote project A, and A's executable. 6. Choose Apply and Run. 7. Shut down resource manager. 8. Choose edit. 9. Initialize connection to remote host B where you have a remote project B 10. Start the manager. If you wish, open RemoteEnvironements tab and check that connection B is indeed running (it should be) 11. Go to the application tab and choose remote project B, and B's executable. (I note something peculiar here: the browser does not immediately find the project directory, but puts me in the home directory on B). 12. Choose Apply and Run. At this point you should see an Error Dialog: "Launching '[launch tab name]' has encountered a problem: Path [A's executable] not found" Al