STM32CubeIDE 1.19 Win10, Error running GDB

Archer_Lawrence · ‎2025-08-04

Hi all,

I recently updgraded to STM32CUBEIDE 1.19 and GDB stopped working.

The error is

I'm a Linux illiterate, and most to the posts seem to be Linux centrix.

Any help is greatly appreciated!

Thanks, Archer

Archer_Lawrence · ‎2025-08-07

Hi Andrew,

Thanks for the reply. I have a work around.

I made the mistake of calling the project the same name as the STM device (i.e STM32F767).

Eclipse got all kinds of lost with that, I renamed the project directory, edited the project file, and erased the workspace. It all went back to working.

Thanks again

Archer

View solution in original post

Andrew Neil · ‎2025-08-05

What does pressing the 'Details' button reveal?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Archer_Lawrence · ‎2025-08-07

Hi Andrew,

Thanks for the reply. I have a work around.

I made the mistake of calling the project the same name as the STM device (i.e STM32F767).

Eclipse got all kinds of lost with that, I renamed the project directory, edited the project file, and erased the workspace. It all went back to working.

Thanks again

Archer

Andrew Neil · ‎2025-08-08

That's interesting!

Please mark that as the solution - it will be useful to be able to find that!

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Amel NASRI · ‎2025-08-13

Hi @Archer_Lawrence ,

That would be a serious issue if project name matching with product part number breaks STM32CubeIDE.

On my side, with same STM32CubeIDE version and Win11, I wasn't able to reproduce the issue. I would like to go farther with check if you can share your ioc file to check on my side.

-Amel

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.