[support]

Hi,

That makes sense. VisualGDB keeps a log of all GDB commands to display them in the GDB Session window, so a log over 700 MB + formatting and timestamps could easily exceed the maximum 2GB allowed per user-mode process.

What happens if you clear the gdb session log from time to time? Does it reduce the memory usage of devenv.exe in Task Manager?

[support]

Hi,

You can then use a combination of an additional startup command in VisualGDB Project Properties and the Raw Terminal (Custom and Ultimate editions only). Simply configure the terminal to connect to the port where Segger forwards the tracing output.

[support]

Hi,

Please try downloading the newest Nordic SDK and replacing the contents of the C:\Users\LabUser\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF52 folder with it.

[support]

Hi,

Normally this should not happen. Can you close the .cpp file, open the View->Clang IntelliSense Diagnostics console, clear it and open the .cpp file again?

The console should show some diagnostic messages explaining why VisualGDB decides to use Clang IntelliSense for this file. If they do not clarify the situation, please post them here so that we could suggest further steps.

[support]

Hi,

Does it work when you run your program manually via SSH? If not, the only advice we could give is to try stepping into the library code and figuring out why it cannot open the device. Perhaps the device is already open by some other app?

• This reply was modified 9 years ago by support.

[support]

Hi,

Good to hear you got it to work. Regarding the size, please try switching to newlib-nano. It significantly reduces the size of your binary.

[support]

No problem. Let us know if you run into further problems.

[support]

Hi,

You should be able to add a normal text file and rename it to .natvis manually.

If this does not help, can you archive the repro project and send it to us?

[support]

Hi,

You should be able to automate this command via the Additional GDB Commands in VisualGDB Project Properties, so there is no need to change anything on our side.

BTW, VisualGDB 5.1 supports a new fast semihosting mechanism that is based on the same technology as Live Variables. It uses a circular buffer inside your program to send semihosting output without stopping the program, resulting in much higher speeds. Please consider giving it a try (you will need to enable it on the Embedded Frameworks page).

[support]

Good to know it works. If you run into further problems, let us know.

[support]

Please try setting the “run GDB as root with sudo” flag in VisualGDB Project Properties.

[support]

Yes, that should help. Also VisualGDB 5.1 Preview 2 automatically verifies _estack by trying to write at _estack – 4 and check that the memory gets actually modified.

[support]

Hi,

Yes, the library should be suited for ARM devices. Furthermore, it should be compiled with the matching CPU type, ABI and floating point settings.

Please ask the vendor for a specific library for Raspberry Pi or the library sources so that you can build it yourself.

[support]

Cool, thanks for sharing this.

[support]

Hi,

Good to know it works, if you encounter any other problems, feel free to create a new topic.

[Author]

Posts