Forum Replies Created
-
Posts
-
Hi,
The toolchain does work by default. In this case it looks like there is a mismatch between different library versions on your Raspberry Pi and resynchronizing the toolchain’s sysroot with your device downloaded those incompatible libraries to the toolchain. Please re-check if it can be reproduced with the default toolchain. If yes, please provide a simple repro project so that we could fix it. If no, please revert to the default Raspberry Pi image to ensure that your libraries are in sync.
Hi,
This looks like a known problem. Please follow the solution described here: http://qt-project.org/forums/viewthread/49098
You can download the debug package manually and install it via command line. Which debug method do you need?
OK, if you get strange build errors, do not hesitate to post them here so that we could suggest a solution.
Sure, have a look at this tutorial: http://visualgdb.com/tutorials/raspberry/qt-cross/
Hi,
The Visual Studio API for providing thread information is quite limited, however we could probably add a context menu item there that will show an extension-provided window with detailed information about the selected thread. Would that work for you?
Hi,
We currently don’t provide a separate toolchain for Raspberry Pi 2. Please try using the old toolchain and resynchronizing the sysroot to replace the headers and libraries with the ones from your device. Once we release a special toolchain for Raspberry Pi 2, we will post an announcement on Twitter.
Hi,
You need to make a post-build action because the header file will be updated during build. Simply use the Custom Actions page in the VisualGDB Project Properties dialog to setup a custom action. Note that you will need VisualGDB Custom Edition and higher.
You can also configure VisualGDB to use a cross-compilation toolchain (i.e. build the code on the Windows machine) to avoid this problem completely.
Hi,
Looks like you are using the Angstrom image for Beaglebone that requires special setup. Please follow this tutorial for details.
Note that you need to use a compatible toolchain. The new Debian-based toolchain will only work with Debian-based images.
Hi,
This looks like a bug in the Android toolchain caused by incompatibility between your Android version and the toolchain version. The only known solution to this is to try different toolchains (selected on the Makefile Settings page of VisualGDB Project Properties). If this does not help, please try another device.
Hi,
Linux kernel debugging is quite tricky compared to user-mode debugging as the debugging infrastructure misses many things that are taken for granted in user mode. E.g. loading symbols for a dynamically loaded kernel mode requires parsing internal Kernel structures and manually specifying section addresses.
We have created a separate product called VisualKernel that greatly simplifies all those tasks and provides out-of-the-box kernel debugging experience for most common Linux distros and we recommend using it for kernel debugging instead of VisualGDB.
Hi,
Please change the file extension to .S.
Note that the EWARM assembler syntax is different from the GNU ARM assembler syntax so you would need to change some directives. You can run the GCC with the -S flag to compile a .c/.cpp file into an assembly file to see a working example of an assembly file for your architecture.
We would recommend creating a basic “LED Blink” project and gradually replacing it with the files from the other project you want to use. This way you would start with a working project and would be able to address build errors (e.g. missing include directories or missing files) one-by-one.
Hi,
Most likely you are missing the UI header file that is generated from the UI definition files on the remote machien as a part of the build. Please locate it on the remote machine and either copy it manually to the Windows machine, or setup a post-build action that will automatically download it after each build.
