Forum Replies Created
-
Posts
-
Are you using VisualKernel to build the kernel itself, or have you already built and installed it manually?
Hi,
VisualGDB also queries the explicit/implicit directories from gcc. Depending on your project type, this is done during the toolchain testing or during the project load.
If you believe it is not working, please let us know your project type (i.e. whether you are using Advanced CMake and whether the project is built on the Windows or Linux machine) and we will help you get it to work.
Thanks for clarifying this. Is it a remotely built Advanced CMake project? If this is the case, VisualGDB tries connecting to the remote machine in order to query the code structure from CMake (this ensures that the project structure shown in Solution Explorer exactly matches what will be actually built).
If you have previously opened the same project on the same machine, you can cancel the connection so that VisualGDB will display the cached project structure, however the project editing functionality that depends on getting updated information from CMake (e.g. adding new files to targets) won’t work.
If you don’t want to have continuous access to the Linux VM, please consider using a Windows cross-toolchain instead. In this case CMake will run on the Windows machine, so no remote connection will be required until you start debugging.
Not sure what you meant. Please try attaching a screenshot of the problem, showing what you are trying to achieve and what you actually observe and we will help you get it to work.
The second last line can be ignored. It just means that VisualGDB closed the connection without issuing the proper shutdown command and it shouldn’t matter for connection tests.
This time it actually looked like a successful test, so you should be able to debug your project now, although all we changed in that build was adding extra logging, so the problem might reoccur later.
Thanks for the update. We have updated the temporary build to include more logging. Please try this one (same link): http://sysprogs.com/files/tmp/openocd.exe
Sorry, not sure what your question was. If you could provide an example of what you are trying to achieve, we should be able to help you find the correct setting.
Thanks for the detailed description. Since this could be caused by a specific version of Boost, could you please share an archive with your MinGW toolchain (including the boost version you are using)?
You can upload the archive to any file sharing service (e.g. Dropbox) and either share a link here, or report it via our support form.
Hi,
This looks like an incompatibility between OpenOCD and your USB driver. Please try replacing the OpenOCD executable in %LOCALAPPDATA% with this one: http://sysprogs.com/files/tmp/openocd.exe
If it doesn’t work, please share an updated OpenOCD output.
No problem. It looks like we will need to know more details about your setup (specific installation IDs) and may need you to run our internal diagnostic tool in order to see what is going on. Please create a support ticket here and we will get back to you with details.
No problem. Just a heads up that you may still qualify for a 50% renewal discount (that will add 1 year to the previous expiration date even if it’s in the past or in the future), Simply use this page to get an automatic renewal quote.
Hi,
This might have something to do with the debug symbol settings. Please follow this tutorial for a detailed explanation of symbol-related settings and troubleshooting tips. If you have any further questions, please let us know more details per tutorial and we will help you understand what is going on.
Hi,
Please ensure you are using MSBuild-based projects, not GNU Make-based ones. The “Excluded from build” flag is only supported when using MSBuild.
If you specifically need to use Make, please consider patching the Makefile instead (conditionally removing specific files from all_source_files using the $(filter-out …) syntax) or adding an #ifdef directive inside the file itself.
No problem, we can walk you through the necessary setup. Please let us know the email associated with your license key (or update your forum profile to match it) and we will be happy to share the detailed instructions.
