0000956: Breakpoints inserted during a debugging session do no take effect

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000956

OMNeT++

IDE / C++ development

public

2016-04-15 09:50

2017-03-02 15:26

Reporter

andras

Assigned To

rhornig

Priority

normal

Severity

major

Reproducibility

sometimes

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

5.0

Target Version

Fixed in Version

5.1

Summary

0000956: Breakpoints inserted during a debugging session do no take effect

Description

Breakpoints inserted during a debugging session do no take effect. The IDE displays the breakpoint normally, however, the program does not stop there. This is a CDT issue which affects all C/C++ programs, not only OMNeT++ simulations. Breakpoints added *before* starting the debugging session work correctly. The workaround is based on this observation: after inserting the breakpoint, simply restart the program.

When setting the breakpoint is unsuccessful, what actually happens is that CDT inserts, then immediately removes the breakpoint. This can be seen in the log of the communication between CDT and the gdb debugger. Just switch to the "gdb traces" console in the Console View using its local toolbar, then check whether the "break-insert" command is followed by a "break-delete" command. If so -- that's the bug.

The related Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=442394 [^]

Tags

No tags attached.

Attached Files

Relationships

Notes
(0001215) rhornig (administrator) 2016-04-15 10:06	In response to the issue we have updated the Eclipse framework to 4.4.2 and CDT to 8.6. While the issue seems less common with this version, it is sadly still reproducible at least on Windows. Further testing is needed whether we should upgrade to CDT 8.8 or try to implement a local patch for CDT.

(0001336) rhornig (administrator) 2017-03-02 15:25	We have upgraded to CDT 9.2 and the issue seems to be gone. Please reopen if you experience it with the latest version.

Issue History
Date Modified	Username	Field	Change
2016-04-15 09:50	andras	New Issue
2016-04-15 09:53	andras	Description Updated	View Revisions
2016-04-15 09:56	rhornig	Description Updated	View Revisions
2016-04-15 10:06	rhornig	Note Added: 0001215
2017-03-02 15:25	rhornig	Note Added: 0001336
2017-03-02 15:25	rhornig	Status	new => resolved
2017-03-02 15:25	rhornig	Fixed in Version	=> 5.1
2017-03-02 15:25	rhornig	Resolution	open => fixed
2017-03-02 15:25	rhornig	Assigned To	=> rhornig