Forum Replies Created
-
Posts
-
Hi,
Not sure why the ‘make clean’ command starts the build. Are you using a custom Makefile?
Please try enabling the verbose mode in Tools->Options->VisualGDB->General->Output and selecting Build->Clean Solution. VisualGDB will then show what exact commands it runs.
If this does not help pinpoint the problem, please post the output of the verbose cleaning here so that we could provide further advice.
Hi,
That’s a known issue. VisualGDB automatically substitutes register names to support data tooltips for inline assembly. As a workaround please use the Locals window or rename your variables.
Hi,
Does the “libatk-1.0.so.0” file actually exist in the toolchain’s sysroot? If no, please resynchronize the sysroot via VisualGDB Project Properties.
Hi,
Could you please try evaluating the variable via the GDB Session window (“print <variable name>”)? Does this show correct values?
Perhaps the variable name is confused with something else, like a global variable with the same name of a register? Does the Watch window show correct value?
Hi,
We do have plans on adding more mbed tutorials, but not before the v5.2 release at the end of summer. If you have some specific topics you would like to see covered, let us know and we will address those first.
Hi,
Please try the __attribute__((__interrupt__(vector))) syntax described here: http://stackoverflow.com/questions/15500826/how-to-declare-an-interrupt-handler-isr-in-mspgcc
Hi,
VisualGDB has its own mechanism for handling signal behavior. Please use the ‘signals’ button in the GDB Session window (the yellow lightning bolt icon). This will set the signal settings properly and remember them for the next session.
Regarding C# debugging, gdb does not support this out-of-the-box, however VisualGDB SDK has an interface for parsing high-level frames (i.e. extracting code location and variable values by manually interpreting the values of the normal C/C++ variables or CPU registers). If you are willing to figure out how to extract that data for Mono frames, yes you can easily hook that up to VisualGDB and we can provide more details on that.
Thanks for reporting this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.1.719.msi
Hi,
So far it looks like a fairly rare scenario that could be easily automated with custom actions, however we’ll keep on watching this thread. If we get more feedback from other users that this would simplify things a lot, we will add it to one of the next releases.
Hi,
VisualGDB already supports mbed. Please see this tutorial for details (step 9 shows how to reference various libraries).
Hi,
Yes, you can right-click on the Source Files folder in Solution Explorer and select “Add->Import Folder Recursively”. VisualGDB will then allow automatically adding all files from a given directory and subdirectories to the project. You can choose to either copy those files to the project directory, or reference them in their current location (that can be a directory shared between several projects as you suggested).
You can also set a checkbox to automatically add all directories containing .h files to the include directory list in your project so you won’t need to do that manually.
Let us know if this does not work.
Hi,
You can do that via custom pre-debug actions. Simply open VisualGDB Project Properties, go to the Debug Customization page and add steps to upload your DLLs. Note that this feature is available in the Custom and Ultimate editions.
Most likely while deleting and reinstalling everything you installed the new version of the debug package that includes the fix as we suggested above.
Now that you have the latest version installed, the problem should not occur anymore.
