Changes

====Mapping for editing====

====Mapping for editing====

Should you wish to actually edit code as well you will need to set up some form of file mapping between the remote copy and your local copy.

Should you wish to actually edit code as well you will need to set up some form of file mapping between the URI that the debugger sends and your 'Server' setup in Komodo

Note that without some of the esmith libraries installed locally you will get some warnings about only being able to open files read only but if you are not actually editing those libraries with warnings can be ignored and the files opened read only to step through

Note that without some of the esmith libraries installed locally you will get some warnings about only being able to open files read only but if you are not actually editing those libraries with warnings can be ignored and the files opened read only to step through

In Komodo preferences you need to setup a Server/Remote Account for the remote server. scp should work.

In Komodo preferences you need to setup a Server/Remote Account for the remote server. e.g.

 

You can then set up a mapping similar to this:

You can then set up a mapping similar to this:

  URI : file://v9-test/etc/e-smith/

  URI : file://v9-test/

  Maps To : /home/john/git/smeserver-libreswan/smeserver-libreswan/root/etc/e-smith/

  Maps To : scp://Test_v9/

 

 

URI : file://v9-test/etc/e-smith

Maps To : scp://Test_v9/etc/e-smith

You should now be able to edit any files that are present on your local machine

You could be more specific about the directories should you require. Remember that you inherit the server permissions - you cannot save a file that is Read Only on the server !

====Multiple machine debug proxy====

====Multiple machine debug proxy====

TBA

TBA