SourceForge has been redesigned. Learn more.
Close

#64 Breakpoint with J-link plug-in

Version 1.x
closed
None
5
2014-07-12
2014-07-08
No

Hi,

I'am using GNU ARM Eclipse Jlink plug-in for debugging my C code, with eclipse Kepler and CodeSourcery Lite ToolChain. I have 1.5.x version.

I have 3 project, 2 static library(A and B), and a "C" a C project. When I debug, I can put breakpoint in A, but not in B, and not in C... Well I can put breakpoint but this message shows up in gdb console :

No source file named C:UsersmeDocumentsProjectHAL STM32F10xmain.c.

I assume it's a backslash issue, but I can't find anywhere an help on that.

ps : gdb console init trace :

monitor clrbp
monitor reset
Warning: the current language does not match this frame.
The target endianness is set automatically (currently little endian)
monitor reset
Register cache flushed.
monitor halt
monitor regs
flushreg
continue
Continuing.

Discussion

  • Liviu Ionescu (ilg)

    yes, it seems to be an Eclipse debugging framework bug.

    except the annoying message, do you notice any functional problem?

     
  • Liviu Ionescu (ilg)

    • status: open --> accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • Liviu Ionescu (ilg)

    you mean the "Using GDB (DSF) Create Process Launcher" setting?

    this is used by default by the j-link plug-in.

     
  • Liviu Ionescu (ilg)

    • status: accepted --> closed
     
  • Liviu Ionescu (ilg)

    this seems a CDT issue that cannot be fixed from the plug-ins.