Forum Replies Created
-
Posts
-
Hi,
If this helps, VisualGDB handles the virtual threads as follows:
- It queries your interface for the registers of each thread
- Then it forces gdb to set current register values to the ones reported by the stub
- Then it asks gdb to list the stack frames
You can diagnose the problem by checking the gdb log to see if VisualGDB sets the registers to the correct values before it asks gdb to list the frames.
GetVirtualThread() is called each time a break happens because VisualGDB does not know which of the threads are still alive.
You might be able to improve the performance if you run your gdb stub remotely, but use Windows gdb from one of our toolchains. It won’t affect the code you build (hence won’t break your certification), but will significantly reduce the latencies for gdb commands.
Hi,
The first error can be caused by the missing ‘extern “C”‘ around the headers if you are using the function from the C++ code.
Regarding the second error, it is hard to tell without a screenshot. Please attach one and we should be able to help you.
Hi,
This makes sense. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.685.msi
It adds support for the EmbeddedThreadPlugin node in the Linux project properties similar to the embedded ones. Let us know if you encounter any problems with it.
Hi,
Thanks for the details, the CMakeLists.txt location is indeed read-only in this case as the wizard makes no distinction between the root source directory (that will be transferred during builds) and the root build directory (that contains CMakeLists.txt). It’s not very trivial to fix, so we have added a note in the 5.2 fix list, but won’t promise anything at this point. As a workaround you can create an empty CMakeLists.txt in the root directory, create the project and then change the CMakeLists.txt location via VisualGDB Project Properties.
Regarding the second missing file, it looks like a separate issue. Is VisualGDB importing the directory contents directly at the root of the project node (e.g. just <project>\main.cpp rather than <project>\dir1\main.cpp)? If yes, please try creating a new virtual folder for your directory, right-clicking on it and then selecting “Import a directory recursively” so that VisualGDB will import the directory contents there.
Hi,
Does the project output any errors to the console? Did you copy the code from the tutorials EXACTLY, or did you modify it? Perhaps you have accidentally bypassed some initialization?
Normally missing libraries should cause link-time errors, but not run-time issues.
Alternatively you can try the same project on a different VM (you can use Vagrant to just download a ready image with some recent OS in just a few clicks).
Hi,
Yes, the global settings like board type are managed per-project. However they are just convenient shortcuts for things stored in nrf5x.mak and debug.mak/release.mak, so you can simply take the -DPCAxxxx setting from nrf5x.mak and put it into per-configuration .mak files modifying each one individually. The only pitfall is that editing global settings in the GUI will regenerate the global .mak file.
Hi,
Yes, please try running it as root. If this does not help, double-check your camera connection, settings and try some other command-line tool for capturing images.
Thanks, we have reproduced it. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.684.msi
Hi,
Currently it is only supported with the Embedded projects that are built locally.Is there any reason you cannot setup a locally built project for your target?
We could also add experimental support for virtual threads to Linux projects if this helps.
Hi,
The easiest way to do that would be to just reinstall the toolchain to c:\ again. The installer will update the registry automatically.
Hi,
Yes, it could be that some access control settings were interfering with saving the changes. If you encounter further problems, feel free to open another topic.
Hi,
First of all, please try running the project on the Linux machine. Does the GUI show correctly? If no, the problem is in the project and not in XMing.
If yes, please try creating a basic Qt project and OpenGL project. If the first one does not show properly, it looks like an Xming bug. If the second one does not, you may be missing OpenGL support.
