cancel
Showing results for 
Search instead for 
Did you mean: 

Breakpoint installation failure unmatched quote

ddwertz
Visitor

Hello. I am currently working on a NUCLEO-L152RE project in the latest version of the CubeIDE. I am running into an error where I can not install break points due to an "unmatched quote". I have tried the common fixes (New work space) for this that I could find online and it hasn't resolved it. I also ran fresh installs of the programs and encountered the same issue. Has anyone else encountered this problem? I have included a screenshot below for reference. 

 

ddwertz_0-1768230405538.png

 

1 ACCEPTED SOLUTION

Accepted Solutions

@ddwertz wrote:

This is the file path shown in the IDE

ddwertz_1-1768235427673.png


I added a PS to my previous post - it looks like the single quote might also upset things...

Check also what "OneDrive - Personal" actually translates to ...

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.

View solution in original post

12 REPLIES 12
Andrew Neil
Super User

Welcome to the forum.

Please see How to write your question to maximize your chances to find a solution for best results

 

In particular, what version of Cube are you using, and on what platform?

Please describe in detail the steps you take to get to this error.

 


@ddwertz wrote:

I am currently working on a NUCLEO-L152RE project


Is this a project you've created yourself, an ST example, or something else?

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.
TDK
Super User

Does the project build and run successfully?

Maybe there is an unmatched quote in the file or a file it includes. It's unlikely to be making things up--this is parsed, not AI.

If you feel a post has answered your question, please click "Accept as Solution".

I am using the 2.0.0 Build of both the IDE and MX software. I used the MX file to generate the initial code and then added some generic lines (incrementing an integer). This is the second project I have created using the MX and they both have the same problem. I am running the software on a Windows 11 set up. As far as I can tell everything functions properly except for the breakpoints.

The project builds and runs as intended. The breakpoint is to be inserted as part of a lab exercise to show functionality.  When I manually stop/start the program it functions as intended, it just won't allow me to insert a breakpoint. As far as the included files I generated it in MX (ver 2.0.0).

Please give detailed steps of what you're doing to get this message.

 

PS:


@ddwertz wrote:

 part of a lab exercise .


So have you shown this behaviour to your lab supervisor?

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.

I have shown it to the TA and he was unfamiliar with it, ended up using the older version of the IDE (1.9.0 I think) to run the labs last week to complete it. I have spoke with the course instructor and he was unsure as well. I reached out to the course instructor over email last Wednesday after performing fresh installs and haven't heard back yet. I am going to the TA office hours today to get more assistance.

 

As far as specific steps, I generated the initial file in the MX (ver 2.0.0). I then opened the project in my CubeIDE workspace (ver 2.0.0). Then I added two lines. The first declared the variable myInt and set the value to 0 "uint8_t myInt = 0;". The second increments myInt in the generated while loop "myInt++;". I only get an error when I add the breakpoint to any of the lines in the main.c file, using both the add breakpoint option and double clicking the line number. 

Adding the breakpoints generates the message, I am getting no other warnings or errors. It has effected every .c file in multiple projects that I have worked on.


@ddwertz wrote:

MX (ver 2.0.0). .


The latest version is 6.16.1 (there's been an update since this announcement).

 

So, after adding your lines, you build the code, and then start the debugger - yes?

Then, once you're in the Debug Perspective, you set the breakpoint ?

 

Are there any spaces or other "special" characters in any of your file or folder names?

 

PS:

Just found this, reporting the same issue in another Eclipse-based IDE, where spaces in the path were, indeed, the problem.

Spaces and other "special" characters are an all-too-common source of grief and weird behaviour - see here.

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.

You're correct in the file version. I mis-listed what I have for it. I downloaded the latest from last Wednesday.

 

Yes, in the Debug perspective I set the breakpoint after adding/building the files.

ddwertz_0-1768235360968.png

This is the file path shown in the IDE

ddwertz_1-1768235427673.png

 

This is the file path as shown in the explorer.

I will remove the spaces in the file names and see if that fixes it.


@ddwertz wrote:

This is the file path shown in the IDE

ddwertz_1-1768235427673.png


I added a PS to my previous post - it looks like the single quote might also upset things...

Check also what "OneDrive - Personal" actually translates to ...

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.