OMNeT++/OMNEST Bug Tracker

View Revisions: Issue #956 All Revisions ] Back to Issue ]
Summary 0000956: Breakpoints inserted during a debugging session do no take effect
Revision 2016-04-15 08:56 by rhornig
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 [^]

Revision 2016-04-15 08:53 by andras
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.

Revision 2016-04-15 08:50 by andras
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* the breakpoint session work correctly. The workaround a based on this observation: after inserting the breakpoint, simply restart the program.

This is a CDT issue. 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.



Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker