[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.

[support]

Hi,

Strange, we have never managed to reproduce that. Which version of the Segger software are you using?

[support]

Hi,

Then we would recommend asking the camera vendor for a C++ project example showing how to use their library. You can then import that example into a VisualGDB project and step through it to understand how it works.

[support]

Hi,

No worries, we’ll help you get it right.

First of all, please use just the function name without brackets (e.g. TestFunc, not TestFunc()). Then if it does not help, run “nm <library name>” without grep to see if the library symbols can be viewed at all.

If ‘nm’ does not provide reasonable output, you can also run “objdump -t <library name>” to list the symbols using another method.

You can also run “stat <library name>” to see the modification time of the library. If you are using the old version you should clearly see it from the modification time.

Remember, your code inside the library must actually call the TestFunc(), as otherwise it will be discarded by the linker as an unused function.”

If nothing helps, please share the output of the nm and objdump commands here.

[support]

Hi,

This error means that the SSH server simply drops the connection. The only way to diagnose this is to reproduce it on a simpler setup (1 machine, 1 project) and experiment with the SSH server settings to see what causes the error. Perhaps deploying a large file or trying to deploy several files sequentially causes the problem.

[support]

Hi,

Thanks, we have reproduced and fixed it in the upcoming Beta 1 (after Preview 2). As a workaround, please use the Debug->Program without debugging command.

[support]

Hi,

You should be able to replace the contents of the <SysGCC>\esp8266\esp8266-bsp\RTOS-SDK folder with the new RTOS SDK in order to update it.

As for the context switching, preventing it may interfere with some internal logic of the ESP8266 drivers, so we would not recommend doing that. To be 100% sure, we would recommend asking he Espressif support, as they have developed the SDK and should know the exact answer.

[support]

Hi,

Not sure which exact setting you mean, but we have added a button to VisualGDB 5.1 Preview 2 that controls whether the code completion popup appears when you press Ctrl-Space or automatically when you start typing.

Simply use the leftmost button with the lightning icon in the completion popup to switch this mode.

[support]

Hi,

Normally you can select the device in VisualGDB Project Properties -> Debug settings. Then VisualGDB will remember it and pass it to the Segger tool so it won’t ask it each time.

Let us know if this does not work.

[support]

Hi,

Thanks for reporting this, looks like the nRF51 port of mbed expects you to program the softdevice separately. We have published a detailed tutorial showing how to edit the linker script to embed the softdevice in your project just like VisualGDB does normally: http://visualgdb.com/tutorials/arm/mbed/nrf51/

As for nRF52, we will happily support it once mbed officially supports it. If there is an unofficial port already, you can run our open-source mbed BSP generator on it and import the resulting BSP into VisualGDB.

[support]

Hi,

OK, please try the latest VisualGDB 5.1 Preview 2. You can tell it that a type A is an alias for type B by adding a .natvis file to your project with the following contents:

<?xml version="1.0" encoding="utf-8"?>
<AutoVisualizer xmlns="http://schemas.microsoft.com/vstudio/debugger/natvis/2010">
  <Type Name="std::vector&lt;int&gt;">
    <AlternativeType Name="IntVector"/>
  </Type>
</AutoVisualizer>

Note that the Type element should not contain any elements other than AlternativeType, otherwise instead of using the normal STL visualizers VisualGDB will actually follow the Natvis rules defined in the .natvis file.

[Author]

Posts