i´m working with the VisualGDB 4.2 in Visual Studio 2012 to program a raspberry pi.
Unfortunately the connection establishment takes a long time. Before i can debug on the devise i have to wait several minutes everytime…. This is really annoying especially by testing small changes…
That should not normally happen. Typically the connection with Raspberry Pi takes less than 10 seconds.
Please try the following to diagnose it:
1. See if your Raspberry Pi CPU is busy doing something else by running the top command.
2. Try addressing it by IP instead of hostname. Does that change anything?
3. Try using Wireshark to see what happens on the network. Is all the time consumed waiting for one packet or are there several packets exchanged in between? Does with the SSH packets, or are there some suspicious ICMP packets in between?
That should not normally happen. Typically the connection with Raspberry Pi takes less than 10 seconds.
Please try the following to diagnose it:
1. See if your Raspberry Pi CPU is busy doing something else by running the top command.
2. Try addressing it by IP instead of hostname. Does that change anything?
3. Try using Wireshark to see what happens on the network. Is all the time consumed waiting for one packet or are there several packets exchanged in between? Does with the SSH packets, or are there some suspicious ICMP packets in between?
Sorry for the late answer!
1. top command shows strange load…
When no connection to VisualGDB is established CPU usage is low (up to 4%) and idle high (up to 90%). When VisualGDB is connected usage is up to 40% and sy (I guess system) up to 60% so idle is around 0%…
This might be an indication that your Raspberry Pi board is doing some heavy math on the public keys. Does the password-based authentication also take lots of time? Does the output of ‘dmesg’ contain anything suspicious about regenerating keys?
When setting up a new connection you can uncheck the “setup public key” checkbox.
If that does not help, try reflashing your SD card with a clean image. It looks like a strange Raspberry Pi configuration bug.