Bug #18628 2012-06-04 10:22
dasjojo
Breakpoints problem with absolute path
I'm cross-compiling for an ARM processor and debug with arm-none-eabi (yagarto) toolchain via gdbserver.
C::B tries to set breakpoints with absolute path, which does not work:
[debug]> break "C:/Work/ARMProject/Main.c:27"
[debug]No source file named C.
[debug]Breakpoint 3 ("C:/Work/ARMProject/Main.c:27) pending.
Adding code from an older version for absolute->relative filename conversion to debuggerstate.cpp:99 would fix this:
[debug]> break "../../ARMProject/Main.c:27"
[debug]Breakpoint 4 at 0x100f38: file ..\..\ARMProject\Main.c, line 27.
- Category
- Debugger
- Group
- Platform:Windows
- Status
- Open
- Close date
- Assigned to
- tpetrov
History
QUOTE: "No source file named C"
It looks like the gdb you use does not handle windows c:/ path correctly. I don't know which version of gdb you use, but I'm using gdb trunk build under msys+mingw, and no such issue. (Note, I'm not using cross toolchain, I'm using native tool chain).