Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327019 - Ensure breakpoint usage is consistent
Summary: Ensure breakpoint usage is consistent
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard: EaseOfUse
Keywords:
Depends on: 289119 292554 308068 308790 310681 311573 314695 318910 321395 306243 315135 315219 318179 323140 324144
Blocks:
  Show dependency tree
 
Reported: 2010-10-05 11:11 EDT by Michael Rennie CLA
Modified: 2012-03-01 14:12 EST (History)
3 users (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 Michael Rennie CLA 2010-10-05 11:11:48 EDT 
There are many failing scenarios for the use of breakpoints in the JSDT debugger. We must ensure that these failings are remedied with either a fix or better user feedback to explain that something failed.

There are three main themes to this:

1. make the setting of breakpoints more informed - ensure that if breakpoint placement fails there is sufficient user feedback to determine why

2. make sure breakpoints remain consistent with source - automatically update as source us edited (see bug 324144)

3. clean up the presentation of breakpoint options - for example 'suspend for all script loads' and 'suspend on all exceptions' could be better presented than a view sub-menu in the breakpoints view.