Forum Replies Created
-
Posts
-
Hi,
Static libraries are just archives containing multiple .o files. As their creation does not involve linking (i.e. combining multiple .o files into a single image), no .map file can be generated for them.
Could you confirm that running the same gdb commands manually (in a gdb instance started from command line) works? If yes, please share the full gdb log (can be enabled on the Advanced GDB Settings page of VisualGDB Project Properties) and we will investigate.
Hi,
VisualGDB takes the list of supported devices from the MCU.CSV file in the Segger Software directory.
It looks like the nRF52840_xxAA device is supported, but not listed there. We will contact Segger support for clarification. As a workaround, please try adding an entry to the CSV file manually so that VisualGDB can recognize it.
Hi,
This could be caused by a bug somewhere in the code (e.g. uninitialized variable or missing ‘volatile’ keyword) that only takes effect when the code is optimized. We would advise locating the code responsible for setting the hardware registers and stepping through it in disassembly mode to understand what is going on.
Hi,
Looks like you are using an older v5.3 Preview build. Please try updating to the latest Preview 7.
OK, we have fixed the expression type reporting in this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.7.1748.msi
It should automatically filter out the base class definition in all cases and only display the actual class name.
Hi,
Please try adding the files from <Nordic SDK>\external\segger_rtt to your project.
Please note that we normally recommend using the VisualGDB Fast Semihosting mechanism instead (can be enabled via the Embedded Frameworks page of VisualGDB Project Properties). It is fully integrated with VisualGDB, supports multiple text colors and its output will be automatically shown in a separate window inside the Visual Studio window while the debugging is active.
Hi,
Thanks, we have fixed this in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.3.7.1748.msi
Hi,
Please try using this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.7.1746.msi
It will display the path that caused the exception.
Hi,
It looks like your trial period has expired. In order to continue using VisualGDB you would need to purchase a license.
Hi,
Thanks for your feedback, we will consider adding a new tutorial about troubleshooting the type visualizer issues.
You can diagnose the lockups by checking the GDB Session window (enable the timing mode to see the time consumed by each command) or the diagnostic gdb logs (can be enabled via Advanced GDB Settings).
Visual Studio supports custom expression viewers (e.g. see the VS HTML viewer) that are displayed when you click the magnifying glass icon on the expression. VisualGDB does not directly support this, however we could easily add one of the 2 options:
- Let you export your implementation of the VS interfaces via your type visualizer
- Extend our type visualizer API to support easy WPF-based custom viewers (this would count as a custom paid feature as it’s very specific and relatively complex).
Let us know if you would like to proceed. If you would like to get a quote for extending the API, please contact us via the support form.
Hi,
We are planning to look into address sanitizer within the next few weeks, although it may end up generating too much overhead for any reasonable scenarios. We will post an update here once we support it.
Hi,
Thanks, this looks like our bug. VisualGDB should normally filter out the “: public …” part. We will investigate and fix it in one of the next builds (this will break compatibility with the current workaround though).
Probe() doesn’t get called if only one visualizer matches the expression via triggers. This is done to reduce the overhead that Probe() might cause (by running extra gdb commands).
