Forum Replies Created
-
Posts
-
Hi,
You can start with compiling your code on the device (follow the Raspberry Pi tutorial). Once that works, you can try using a Raspberry Pi cross-toolchain and re-synchronizing its sysroot so that the headers/libraries contained in it get overwritten by the files from your device.
Let us know if that works.
Hi,
The “error 0” usually indicates that the root password is empty. Please set it to a non-empty one and VisualGDB will be able to connect.
Hi,
Sorry for being ambiguous. Please install the Beaglebone drivers. Once installed, they will create a virtual COM port (look in Device Manager for details) that should give you access to the Beaglebone console.
Then the simplest solution would be to use that newer NDK version in your debug configuration (the release one that does not need to be debugged can still be built against an older NDK).
Hi,
Your log does not contain any -break-insert commands except for the original breakpoint in main(). Are you sure your breakpoints are enabled?
Hi,
That is not possible. However you can start your service as “gdbserver : myservice” and then use the “target remote :” command to attach to it with VisualGDB.
Hi,
Do you have the ssh server running on the beaglebone? Can you connect to itself via SSH (type “ssh localhost” via the USB console)?
Hi,
Are you able to use the non-stop mode reliably in the normal command-line mode without VisualGDB?
Hi,
This might be happening because you are building against an older platform version in NDK that installs an older gdbserver (tool required for debugging) that is incompatible with the new Android OS.
Does switching the NDK platform to a more recent one solve the problem?Hi,
Last time we checked the GDB non-stop mode, it was not very reliable and many commands did not work in it. Could you please let us know what are you trying to accomplish with using the non-stop mode? There could be a better solution to that.
Hi,
This cryptic message actually comes from Windows and means that the host name you specified cannot be found. Please try stopping your DNS cache service (net stop dnscache) or specify the IP address directly.
Hi,
We are currently still investigating the feasibility of building the 4.8 toolchain. So far we have managed to update our Raspberry Pi device to Jessie, but there are still some things to figure out before we can publish the toolchain.
Hi,
Normally VisualGDB will compute relative source file paths and put them to Makefile when updating it. Looks like in your case this mechanism is not working as expected. Could you please share your Makefile and also let us know its full path, the full path of the .cpp file and the full path of the Visual Studio project?
Hi,
It’s hard to say where exactly the problem is, but it’s somewhere between your GDB and the GDB stub. The GDBServer protocol uses hardcoded register positions, so if the stub and GDB make different assumptions about them, things will be mixed up.
We would advise using VMWare GDB stub instead (e.g. http://sysprogs.com/VisualKernel/tutorials/vmware/). You can also try explicitly compiling your GDB with XML support so that it will understand XML register descriptions reported by the stub (if Bochs supports them). If that does not help, the solution would be to dump the packets received from the GDB stub, compare the reply from Bochs with the reply from normal GDBServer and adjust the Bochs sources to make them compatible with GDB.Hi,
This is a known limitation of recent Android versions. In short, you will need 2 versions of your native tool: one for Android 4.1+ and another one for the previous versions. Running the older one on the new OSes will show the message you are experiencing. You can read more about it here: http://stackoverflow.com/questions/24818902/running-a-native-library-on-android-l-error-only-position-independent-executab
