#130 Break point issue when there are spaces in the file path

[Stefano Oliveri]

Configuration info

• Plug-in version: 2.4.1-201410142110
• Eclipse version: Kepler SR2 (4.3.2) 64bit
• Java version: 1.7.0_72-b14 64bit
• Operating system: Windows 7 64bit
• Toolchain version: arm-none-eabi-4_8-2014q3

Problem

• I create a default Blinky project for STM32F501 MCU inside a folder with a space in the path like "C:\ODeV_LH\Bad folder\STMF051_Bad\"
• I add a simple function in the main.c file like "void foo(int n) { (n)++; }" and I add a call to foo in the main function
• I start a debug session (ST-Link/V2 + OpenOCD)
• When I add a function breakpoint from the Outline view:
  • The breakpoint annotation is displayed in the editor
  • The breakpoint doesn't work
  • An error is reported in the gdb traces console (see Case 1 in the attached file)
• When I add a function breakpoint from the GDB console (b foo):
  • It works fine (See Case 2 in the attached file)
• Case 3 in the attached file shows that a native application debugged using Cigwin (GNU ARM Plugin is not used) doesn't have this problem

Do you think it is a bug of your great plugin?

Regards,
Stefano

[Liviu Ionescu (ilg)]

I got the point, it looks like the Windows path is not processed correctly, while both are path are POSIX paths.

unfortunately my plug-ins do not deal with setting breakpoints, this is done by Eclipse :-(

[Stefano Oliveri]

So in your plug-ins you don't have extended the DSF-GDB's command factory in order to easy modify the MI command when needed.

According to your experience, why I can't reproduce the problem when using Gygwin for a native win32 application?

Regards,
Stefano

[Liviu Ionescu (ilg)]

why I can't reproduce the problem when using Gygwin

because Cygwin uses POSIX paths.

the problem seems to be with windows paths, the backslashes are interpreted as escapes, not as path separators.

[Stefano Oliveri]

f.y.i.

I found a workaround. The OpenOCD folder hierarchy in my case is the following:

• <openocd_root></openocd_root>
• bin
• bin-x64
• scripts
• source

I use the -s option to tell OpenOCD where to look for the configuration file. It works fine with relative path (to the openocd executable). So for example I use a config options like this:

-s ../scripts -f interface/stlink-v2.cfg -f target/stm32f4x_stlink_freertos.cfg

It works fine on Windows host.

Regards,
Stefano

[Liviu Ionescu (ilg)]

so the problem is not related to breakpoints at all, it is related to starting OpenOCD properly.

did you install OpenOCD using the setup, exactly as described in the documentation?

regards,

Liviu

[Stefano Oliveri]

OpenOCD starts, and I have installed it using the setup.

I had the problem with the breakpoint as I described in the first post. My feeling is that there is some problem with the path passed as argument to the break-inset command. This problem doesn't occur if I change the way to start openocd. I will check again the gdb trace console and to find some other (useful) information.

Regards,
Stefano

[Liviu Ionescu (ilg)]

any progress?

[Stefano Oliveri]

Hi Liviu,

After updating Eclipse to the last version - Luna SR1a - the problem is no more present.

Regards,
stefano