CubeIDE 2.1.0: Still opening spurious files when starting a debug session

[padawan]

Title edited to state the issue being discussed.

---

Really? After all these years?

 

Padawan

[TDK]

> Really? After all these years?

Yes.

This isn't a new issue, just the first time it's in the errata.

Acknowledging the problem is the first step. This is progress.

[padawan]

Hi TDK

not the first  time 

 

So the knew it since years.

https://community.st.com/t5/stm32cubeide-mcus/jumping-to-random-file-after-pressing-run-button/td-p/246693/page/23

padawan

[mƎALLEm]

Hello @padawan ,

According to an internal information that seems to be an Eclipse related issue. We need to wait for the Eclipse fix before to integrate it in CubeIDE.

[vaualbus]

Cannot you solve yourself or try to mitage it somehow?

I suggested in the past to at least make the file temporarily read-only until the run/debug operation has not hit the main so that random file is not changed if some input is issued while the random file is opened. That seems an "easy" solution at least it mitigates some annoying

[MGogr.1]

Not an New issue.

It has been there for quite a long time now.

[padawan]

Hi Andrew,

if i have to work a round a bug, there is still a bug ;)

And: this bug is very old (and still a bug, not a feature).

At the first postes about this bug they say, they solve it "asap"

Now, over 5 years later, i think "asap" is a long time. :)

I will go to tell it my wife, if she wants to make me  clean up the garage.

"asap my dear"  

padawan

(edit typo)

[Andrew Neil]

---

@padawan wrote:

if i have to work a round a bug, there is still a bug

---

Of course - that's why it's called a workaround - not a fix !

This issue with CubeIDE 2.1.0 opening spurious files when starting a debug session has been reported by several users and is usually related to the IDE automatically opening source files linked to the debugger’s last context or saved workspace state. When a debug session starts, the IDE attempts to restore previously opened editors or jump to the current program counter location. If the workspace contains cached references or outdated debug information, CubeIDE may open unrelated or unexpected files.

One common solution is to clear the IDE’s saved workspace state. You can try closing all open editors, saving the workspace, and then restarting CubeIDE. Another helpful step is to go to Window → Preferences → Run/Debug → Launching and disable options related to restoring previous debug sessions or automatically opening source files. Sometimes deleting the .metadata cache inside the workspace (or starting with a fresh workspace) can also resolve the issue if the problem is caused by corrupted settings.

Additionally, make sure the project is properly cleaned and rebuilt before debugging. Go to Project → Clean and then rebuild the project so the debugger references the correct source files. Updating to a newer version of STM32CubeIDE can also help, as many debugging and editor-related bugs were fixed in later releases. If the problem continues, checking the Debug Configurations and removing unused configurations may prevent CubeIDE from opening unexpected files during startup.

wafflehouse.us