Forum Replies Created
-
Posts
-
Hi,
Thanks, this looks like a bug fixed a few maintenance builds ago. Please update to the latest VisualGDB 5.3R8.
Hi,
No problem. Please let us know what are you trying to create a – stand-alone command-line Android tool, a native Android app or a Java App with C++ part built by CMake.
Hi,
Thanks for the screenshot. This type of output is processed directly by Visual Studio and should not be affected by any VisualGDB bugs. If you observe the same in Android Studio, this is likely a bug in Gradle.
Hi,
This is by design – VisualGDB normally keeps automatic rename smart tags for 3 last edits. You can disable this by setting this limit to 0 as shown below:
Please note that you would need to reopen your project after changing this setting.
Hi,
Normally the Clang IntelliSense should automatically pick this flag from the project settings. If not, please try adding it to VisualGDB Project Properties -> IntelliSense Settings -> Additional flags for C++ files.
Hi,
As we are not a vendor for Segger RTT, unfortunately we cannot provide much help for this. For VisualGDB projects we recommend using our advanced semihosting framework (enabled via the Embedded Frameworks page of VisualGDB Project Properties). It provides fast non-stop semihosting (including support for multiple colors via the ANSI escape sequences), is fully integrated with VisualGDB and doesn’t need any extra setup.
Hi,
Thanks, this might be related to a recently fixed bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.2008.msi
Hi,
That would normally count as a valid attempt to rename the function. If this is annoying, we could easily add an option to disable this behavior.
Hi,
The shortcut actually comes from Visual Studio. You can see under in Edit->IntelliSense together with a other IntelliSense commands. If you are not familiar with Visual Studio commands and shortcuts, we would advise looking through the Edit menu – it contains a few very powerful commands.
Hi,
Sorry, unfortunately that is not directly supported. However as for CMake projects the Solution Explorer contents is dynamically built from the CMake project structure, you can simply copy-paste the CMakeLists.txt file structure to a newly created project (and also copy all relevant sources) and VisualGDB will automatically update Solution Explorer to show the contents of your project.
Hi,
Strange, normally this would not happen. Does this happen in the Output window (the regular Build Output pane?)? Could you please share a screenshot so that we could see if anything else could provide a hint to the cause behind this?
Hi,
You can achieve this by adding “-j<# of cores>” to the Make Command -> Customize -> Arguments. You can also use the $(LocalMultiThreadedBuildFlags) expression instead of “-j<#number>” to let VisualGDB automatically query the number of cores from your system properties.
Hi,
Stopping in “HardFault_Handler” usually a problem in the firmware you are trying to debug (e.g. trying to access an invalid memory location).
The most likely reason for this behavior is incorrect memory layout. You can easily diagnose this by creating map files both in Eclipse and VisualGDB and then comparing them (e.g. check locations/sizes of .text and .data sections, stack pointer/etc). If you get stuck, please try attaching both map files here and we will try to check them for common errors.
Hi,
This looks like the renaming smart tag that should normally appear when you rename a function declaration (it would let you automatically adjust the references). If it’s triggering on a function call, most likely you did not include the header file with the function declaration, so Clang treats your call as an implicit declaration. Please include the correct header file in your sources to fix this.
