[MystikReasons]

Thanks for the reply. I will wait until you do a research in Q3 2019.

Another question: Would it be possible to tell us what you are planing to do in 2019 in form of a roadmap?

Or is it a secret? 😉

[MystikReasons]

I can confirm this problem (Clang Intellisense) in version 5.4 build 2737 with Visual Studio 2017 version 15.9.6

On some projects it just works fine and on others it won’t work at all so I had to switch to the regular VC++ Intellisense until this is “fixed”.

I only can confirm this problem on some Embedded Projects.

[MystikReasons]

Update: So I found something interesting under Build 2645.

If I always close the GDB session window while debugging and then restarting it always opens it up again and focuses on it.

But if I just change the tab for example to “Autos” and then restarting its not changing to the GDB session window.

 

[MystikReasons]

Update: Also tried Build 2645 and its still the same error.

[MystikReasons]

That sounds nice!

Looking forward to it 🙂

I wish everybody a happy new year!

[MystikReasons]

Hello

Sorry for reviving this thread again but I’ve got a problem with the session window.

I’ve disabled the automatic activation of the GDB session window under: Tools->Options->VisualGDB->General->GUI->Don’t Activate GDB Session window

but in the version: 5.4 Beta 1, Build 2638 it still shows up if I start to debug.

Also if I try to close it, it shows up again in the next debugging session.

The other setting to ignore the inline gdb stub output is working fine.

 

[MystikReasons]

Update: Now it seems to work. Maybe it was a glitch or something

You can close this thread.

[MystikReasons]

My problem right now is that I cant create a C++ project with STM32CubeMX but with VisualGDB I can.

So I always have to add the missing files manually

[MystikReasons]

Thank you for the implementation of the new option to ignore the stub output as well the way to disable the GDB session window.

It really feels better now to debug 🙂

[MystikReasons]

Hello,

Thank you for the link for the tutorial now they are being created and I dont have the error anymore.

Why aren’t they part of the basic project templates? Aren’t they necessary files?

And thank you for the explanation about the function of the “Inline GDB Stub Output” window.

[MystikReasons]

I’m using the GCC ARM toolchain

Question on the side: What does the adress mean in the “Inline GDB Stub Output” window?

And is there an option to see whats in the adress?

Example: halted: PC: 0xffffffffe

• This reply was modified 6 years ago by MystikReasons.

[MystikReasons]

Try this one: https://circuits4you.com/2017/12/08/esp8266-external-interrupt-example/ or this https://techtutorialsx.com/2016/12/11/esp8266-external-interrupts/

[MystikReasons]

Update: Tried to add stm32f4xx_it.c e and got two errors: main.h and stm32f4xx_it.h are also missing (VisualGDB is also not creating this file)

• This reply was modified 6 years ago by MystikReasons.

[MystikReasons]

I have only the embedded version so it makes sense that I can’t see it.

Thank you for your answer.

[MystikReasons]

Thank you for your answer. Now I see my device in the device list.

But I have another question: Under the project properties I cant see the window for the Keil Components (example: CMSIS, RTOS…), see attached screenshot.

In your blog about the newest update of visual gdb (prev. 10) there is a window for the Keil Components.

Is it not fully supported yet?

 

Attachments:

You must be logged in to view attached files.

[Author]

Posts