Bug 283191 - [breakpoints] not handling failed breakpoint after modification
Summary: [breakpoints] not handling failed breakpoint after modification
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 6.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-10 15:40 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:20 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2009-07-10 15:40:31 EDT 
I can modify a breakpoint that was successfully installed, to make it fail installation.  This should trigger a problem marker.  It currently does not.

To reproduce:
1- insert infinite loop in program
2- start a debug session with a bp before the loop.
3- breakpoint is properly installed
4- modify the breakpoint to a line that is after the loop
5- new installation fails
6- there is not problem marker
Comment 1 Marc Khouzam CLA 2009-07-10 15:44:26 EDT 
Oh, and also, after the second installation fails, the breakpoint is still updated to the new one in Eclipse, while we keep the old one in GDB.

So, either we set a problem marker and delete the old GDB bp, or we revert the eclipse bp to the previous one.