Difference between revisions of "PB:Debug local and remote"

From Klaus' wiki
Jump to: navigation, search
 
Line 4: Line 4:
  
 
<source lang=bash>
 
<source lang=bash>
$] cd /opt/toolchains/gnueabihf
+
] $ cd /opt/toolchains/gnueabihf
$] find . -name gdbserver
+
] $ find . -name gdbserver
 
</source>
 
</source>
 +
 +
== Allow root login ==
 +
 +
It can be handy to be able to develop on your development host and transfer the program to the PB, and debug or execute the programs on the PB. In order for this to happen a little change is needed. Debian distributions do - out of security reasons - not allow the user root to login over e.g. ssh. But this can be changed.
 +
 +
As root on the PB do:
 +
<source lang=bash>
 +
] $ vi /etc/ssh/sshd_config
 +
</source>
 +
add this line at the end of the file (navigate to the end using Shift+G in vi)
 +
PermitRootLogin yes
 +
save the configuration file and now the ssh-daemon needs to be restarted.
 +
<source lang=bash>
 +
] $ systemctl restart sshd.service
 +
</source>
 +
Now you can configure a new connection on your Eclipse Remote Debugging setting page. This time the user is root and not your personal login.

Latest revision as of 13:10, 13 November 2018

The instructions given over at Remote Debugging works fine for the PocketBeagle.

To find the gdbserver use these commands:

] $ cd /opt/toolchains/gnueabihf
] $ find . -name gdbserver

Allow root login

It can be handy to be able to develop on your development host and transfer the program to the PB, and debug or execute the programs on the PB. In order for this to happen a little change is needed. Debian distributions do - out of security reasons - not allow the user root to login over e.g. ssh. But this can be changed.

As root on the PB do:

] $ vi /etc/ssh/sshd_config

add this line at the end of the file (navigate to the end using Shift+G in vi)

PermitRootLogin yes

save the configuration file and now the ssh-daemon needs to be restarted.

] $ systemctl restart sshd.service

Now you can configure a new connection on your Eclipse Remote Debugging setting page. This time the user is root and not your personal login.