Forum Replies Created
-
Posts
-
Hi,
It looks like you are trying to link the Crypto++ library compiled for Win32 with the VisualGDB project for Edison. As the library is incomptaible with the Edison toolchain, it simply ignores it.
Please build the library using the same cross-toolchain you use for your project and link to the cross-compiled version of the library instead.
Hi,
VisualGDB navigation bar also supports the ‘Go’ button. It also parses the preprocessor definitions and allows going to either the definition itself, or one of the functions/types contained in the definition:
Hi,
Yes, our .pro file parser is very basic and does not support conditionals. As a workaround, you can disable deployment, add custom deployment actions specifying your target name and explicitly specify the modified target name as the program to debug.
Hi,
The “regenerate MCU files” button is only available starting from the Custom edition.
If you are using the Embedded or Linux edition, you can simply change something on the Makefile Settings page (e.g. add a space to CFLAGS and delete it) and press “Apply”.
Hi,
The main project needs to reference the library projects. Then VisualGDB will automatically grab the path mappings from them when debugging the main project.
Alternatively you can specify the mappings for the library sources manually via VisualGDB Project Properties -> Path Mapping.
Hi,
We did test that (made the temporary directory unwritable, then changed some settings, clicked ‘apply’ and then ‘cancel’ when VisualGDB complained about the directory). The settings were saved properly.
Perhaps the problem you are observing only affects some specific settings? Could you provide a more detailed description:
- What setting are you modifying
- When exactly do you cancel the test
- What do you expect to be changed
- How do you verify that it’s not changed
This should help us reproduce the problem on our side.
Hi,
The live variables are normally stored in the .vgdbsettings.user files. Perhaps your file is not writable and VisualGDB cannot update it properly? Either way, you can delete the file to reset all per-user settings like live variables.
Hi,
If you are using the Clang IntelliSense engine, VisualGDB actually provides its own navigation bar that is better than the VS one. If you don’t want to use it, simply disable the Clang IntelliSense via Tools->Options->VisualGDB->General and Visual Assist will taker over. Note that Visual Assist is not as good with GCC-specific header files as VisualGDB IntelliSense is.
Hi,
VisualGDB 5.x should still save the settings if you cancel the toolchain test. If it doesn’t could you let us know the exact repro steps? Perhaps some specific setting it not saved?
Regarding the temporary directory, you can actually change it for each host individuall via Tools->SSH Connection Manager->Host-wide settings. E.g. you can create a writable directory under your home directory and choose it.
Hi,
Thanks for reporting this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.674.msi
Hi,
Sure, you can do that easily with our VisualGDB product. We have a very detailed tutorial available here: http://visualgdb.com/tutorials/esp8266/openocd/
Hi,
It’s hard to say what could be wrong without seeing the hardware. Have you copied SystemClock_Config() from a proper example for your board? This function varies slightly between different boards.
If yes, we would need to first get debugging to work before we could give any further advice. Could you attach the full gdb log and the OpenOCD output so that we could see why the debugging is impossible?
