Forum Replies Created
-
Posts
-
Hi,
What ethernet card are you using? Kgdboe (Ethernet debugging transport) can be incompatible with some cards. What happens if you try setting up KGDBoE manually (http://sysprogs.com/VisualKernel/kgdboe/tutorial/)? Do you get a connection? Do you get any errors in dmesg?
Hi,
If you are using a Custom or Ultimate edition, you can add a custom pre-build steps to upload as many files/folders as you want. If not, you need to pick one root source directory (so that all source files are located in it or its subdirectories) and set it as your source directory on the Project Settings page of VisualGDB Project Properties.
Hi,
Is your handler function defined in a C++ file? If yes, it needs to be surrounded by extern “C”:
extern "C" void SysTick_Handler() { //... }Hi,
We have investigated this more. When you debug a custom APK file with VisualGDB it checks all EABIs that are present in the APK file and ensures that the library directories for them are present in your library location. Looks like in your case the APK file contains an armeabi version of the libraries, but your library directory does not have them. You can resolve this in one of 2 ways:
* Remove other EABIs from the APK file
* Provide debug versions of all libraries in the APK file for all platformsYou can also press the ‘ignore’ button in the error window to ignore the missing libraries and start debugging nonetheless. If your device EABI is armeabi-v7a, the missing armeabi directories should not affect debugging.
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 conditionPlease 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 == 3If 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.
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.
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.
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).
