Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327114 - Need to distinguish successfully and unsuccessfully set breakpoints.
Summary: Need to distinguish successfully and unsuccessfully set breakpoints.
Status: CLOSED WORKSFORME
Alias: None
Product: PTP
Classification: Tools
Component: Debug UI (show other bugs)
Version: 5.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-06 10:50 EDT by Xuan Chen CLA
Modified: 2016-06-02 11:21 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 Xuan Chen CLA 2010-10-06 10:50:36 EDT 
If I set a breakpoint on a blank line, SDM sends back EVENT_DBG_ERROR.  But this breakpoint is still shown in the prefix area of the editor, and there is no difference between this unsuccessfully set breakpoint and a successfully set breakpoint.  It could be very confusing to the user.
We need a decorator to the breakpoint marker to make the distinction.
Comment 1 Greg Watson CLA 2010-11-01 12:41:45 EDT 
I'm unable to reproduced this. When I set a breakpoint on a blank line, the breakpoint is set on that line. When resuming the program, the target may suspend at a different line than expected. This is the expected behavior and is consistent with how gdb handles breakpoints.

Can you set a breakpoint manually using gdb and provide the output (error message, etc)?