Nsight eclipse

Hi,

I have connected my jetson and my host computer by ssh, to develop on the host computer using nsight eclipse.

I can build and run code on the target (run as remote, build as remote)
Furthermore, I can debug (debug as remote) the CPU but I can’t debug GPU (my host computer doesn’t have cuda capabilities, but it should not be a problem). When I enter in glolab function, the debugger crash, impossible to terminate the debugging … Do you have an idea of the problem ?

Moreother, to profile, does the host computer need to have cuda capabilities ? Because I can’t profile the code.
Last question, can I use a windows host computer ?

Thank you !

Furthermore, I always have the following message when I debug :
[…]
Warning: Adjusting return value of linux_common_core_of_thread (pid=989, tid=989).
core = 5 >= num_cores = 4!
Warning: Adjusting return value of linux_common_core_of_thread (pid=990, tid=990).
core = 5 >= num_cores = 4!
[…]

And this is not a problem from the code, it a sample hello word, which doesn’t use GPU :
#include"iostream"

int main () {

std::cout << "Hello word 1 !" << std::endl ;
return 0 ;

}

Hi,

Here are some information share with you first.

1. Profiling tool requires root authority.
Please login the device as root and here it the detail for setting:

2. There is a known issue in CUDA 10.0 or earlier.
The issue is related to debugger memory backend and is fixed in CUDA 10.1.

***Warning: Adjusting return value of linux_common_core_of_thread (pid=989, tid=989).***
***core = 5 >= num_cores = 4!***

Thanks.

Hello,

Thank you for your answer.

I modified the sshd_config but it still doesn’t work. Here my sshd_config :

#OpenBSD: sshd_config,v 1.101 2017/03/14 07:19:07 djm Exp

#This is the sshd server system-wide configuration file. See
#sshd_config(5) for more information.

#This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

#The strategy used for options in the default sshd_config shipped with
#OpenSSH is to specify options with their default value where
#possible, but leave them commented. Uncommented options override the
#default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

#Ciphers and keying
#RekeyLimit default none

#Logging
#SyslogFacility AUTH
#LogLevel INFO

#Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

#Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2
#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

#For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
#Change to yes if you don’t trust ~/.ssh/known_hosts for
#HostbasedAuthentication
#IgnoreUserKnownHosts no
#Don’t read the user’s ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

#To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
PermitEmptyPasswords no

#Change to yes to enable challenge-response passwords (beware issues with
#some PAM modules and threads)
ChallengeResponseAuthentication no
#Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

#GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

#Set this to ‘yes’ to enable PAM authentication, account processing,
#and session processing. If this is enabled, PAM authentication will
#be allowed through the ChallengeResponseAuthentication and
#PasswordAuthentication. Depending on your PAM configuration,
#PAM authentication via ChallengeResponseAuthentication may bypass
#the setting of “PermitRootLogin without-password”.
#If you just want the PAM account and session checks to run without
#PAM authentication, then enable this but set PasswordAuthentication
#and ChallengeResponseAuthentication to ‘no’.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

#no default banner path
#Banner none

#Allow client to pass locale environment variables
AcceptEnv LANG LC_*

#override default of no subsystems
Subsystem sftp /usr/lib/openssh/sftp-server

#Example of overriding settings on a per-user basis
#Match User anoncvs
#X11Forwarding no
#AllowTcpForwarding no
#PermitTTY no
#ForceCommand cvs server

Ok great. When cuda 10.1 will be available for jetson TX2 ? And will I need sdkmanager to update the jetson ?

Thank you !

To give more details, the profiler give the following message in the console :
======== Warning: OpenACC Profiling is not supported on the underlying platform.
[Vector addition of 50000 elements]
logout

I launched Addvector cuda example

Hi,

I have updated the detail steps for VectorAdd on the below topic:

Let us check the following status on topic 116720 directly.
Thanks.