[support]

Hi,

You can change the output directory on the Makefile Settings page of VisualGDB Project Properties. However, if you have several projects in the same directory, you would need to change the Makefile names for them (same page of properties) to ensure that they are using different Makefiles and their settings are stored separately.

[support]

Hi,

Please check your link command line in the build output. Does it include the ftk.o file twice? If yes, please ensure that you don’t have two different ftk.c files in your project.

[support]

Hi,

Unfortunately that won’t work because the Play Store apps contain release versions of the libraries that simply don’t have debug symbols required for debugging. So even if you manually set the ‘debuggable’ attribute and copy gdbserver, you won’t be able to get any meaningful debugging experience.

[support]

Hi,

Last time we checked the PIC32 devices were not very popular and the popularity was declining. So unless this trend changes, we won’t be supporting them directly.

You are welcome to try creating a project manually by following our legacy device tutorial and feel free to ask questions if anything breaks or becomes unclear.

[support]

Hi,

Please try manually locating the source file that contains the main() function. Is it located under the source directory you are importing?

[support]

Hi,

It’s usually displayed via Help->About VisualGDB. If you want to upgrade, simply email sales@sysprogs.com and we’ll give you a quote.

[support]

Cool. If you encounter any further problems, let us know.

[support]

Hi,

Good to know it works now. It’s hard to say what could be causing the wifi_set_opmode() bug, can be that a simple rebuild just fixed it. If you encounter it again, feel free to let us know.

[support]

Hi,

You can do it by defining a custom pre-debug action (upload a file). Note that this works on Custom and Ultimate editions only.

[support]

Hi,

We have added a workaround to the “Command line too long” problem in this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.617.msi

Let us know if this works.

[support]

Hi,

Thanks for reporting this. We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.613.msi

[support]

Thanks for verifying this. We have updated our ESP8266 toolchain to include the fix.

Please try the r5 build from here: http://gnutoolchains.com/esp8266/

[support]

Hi,

Yes, we are planning to add project templates to VisualGDB 5.1

[support]

Hi,

We have fixed this in the updated nRF5x BSP. Please download the new version via Tools->Embedded Tools Manager.

[support]

Hi,

Strange. If you are sure that the output window did not contain any other text or error messages, please feel free to send us the project causing this so that we could fix that. If VisualGDB skips some relevant error messages, we would rather fix it.

[Author]

Posts