[support]

Hi,

We actually do support conditional breakpoints and hit count. However you may encounter problems with this features if:
* You are using an old gdb that does not support them
* Your symbols do not have information about the variable you are using in the condition

Please try reproducing it on a very simple scenario:

for(int i = 0; i < 10; i++)
{
printf("%dn", i);
}

Your GDB log (GDB Session -> View Mode -> All GDB Interaction) should contain something similar to this:

-break-insert -f /tmp/VisualGDB/e/PROJECTS/TEMP/LinuxProject9/LinuxProject9.cpp:19
^done,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x080488b8",func="main(int, char**)",file="LinuxProject9.cpp",fullname="/tmp/VisualGDB/e/PROJECTS/TEMP/LinuxProject9/LinuxProject9.cpp",line="19",thread-groups=["i1"],times="0",original-location="/tmp/VisualGDB/e/PROJECTS/TEMP/LinuxProject9/LinuxProject9.cpp:19"}
-break-condition 2 i == 3

If it does not work, do you see any error messages when VisualGDB sets the condition? If the basic sample scenario works, but the more complex one does not work, please recheck your symbols.

[support]

Hi,

What VisualGDB/Visual Studio versions are you using? Does reinstalling VisualGDB help?

[support]

Hi,

Which version of VisualGDB are you using?

[support]

Hi,

Please try this build: http://visualgdb.com/tmp/VisualGDB-4.3.10.230.msi
First go to the Custom Debug Steps page and set the break-in method to the “interrupt” command. Then save your settings, open the .vgdbsettings file in a text editor and set the following fields:

true

true

Let us know if that works for your setup.

[support]

If your DHCP server is not configured to automatically send DNS updates for its clients (such as beaglebone), the easiest way would be to hardcode the IP address in %SystemRoot%SYSTEM32Driversetchosts.

[support]

Hi,

What is the EABI of your device (run “adb shell getprop ro.product.cpu.abi” to query it)?

[support]

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.

[support]

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.

[support]

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.

[support]

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).

[support]

Hi,

Your log does not contain any -break-insert commands except for the original breakpoint in main(). Are you sure your breakpoints are enabled?

[support]

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.

[support]

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)?

[support]

Hi,

Are you able to use the non-stop mode reliably in the normal command-line mode without VisualGDB?

[support]

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?

[Author]

Posts