Bug 474157 - Eclipse does not send breakpoints to GDB on remote debug
Summary: Eclipse does not send breakpoints to GDB on remote debug
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: Next   Edit
Hardware: All All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2015-08-03 11:30 EDT by Lucas Grijander CLA
Modified: 2020-09-04 15:25 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Grijander CLA 2015-08-03 11:30:54 EDT
When debugging a remote project, by attaching to an already running one, eclipse does not send the breakpoints to GDB, I have to type manually "break source.cc:22" in the GDB console in order to get it. There are no traces of activity in the GDB-traces console when setting/deleting breakpoints with the Eclipse IDE.

Thank you.
Comment 1 Sarika Sinha CLA 2015-08-05 09:56:17 EDT
This will be an enhancement.
Comment 2 Lucas Grijander CLA 2015-08-06 06:35:44 EDT
(In reply to Sarika Sinha from comment #1)
> This will be an enhancement.

The breakpoints blue dots are displayed in the source, but they are not working, so this seems more like a bug.

The rest of the debug functionality works, step over, step into, view/change variable values,....
Comment 3 Lucas Grijander CLA 2015-08-06 06:38:14 EDT
(In reply to Lucas Grijander from comment #2)
> (In reply to Sarika Sinha from comment #1)
> > This will be an enhancement.
> 
> The breakpoints blue dots are displayed in the source, but they are not
> working, so this seems more like a bug.
> 
> The rest of the debug functionality works, step over, step into, view/change
> variable values,....

A part from the blue dots, the breakpoints are also listed in the breakpoints list, but don't work.
Comment 4 Thomas McLeod CLA 2018-11-15 13:02:28 EST
Any update on this issue?