Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319086 - [breakpoints] Breakpoints skipped by "Skip All Breakpoints" button in breakpoints view should have an explanation.
Summary: [breakpoints] Breakpoints skipped by "Skip All Breakpoints" button in breakpo...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-07 04:25 EDT by Stefan Fussenegger CLA
Modified: 2019-05-03 16:17 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Fussenegger CLA 2010-07-07 04:25:45 EDT
Build Identifier: 20100617-1415

I've just struggled with skipped breakpoints due to an unintentionally enabled "Skip All Breakpoints". I've checked the hover text and breakpoint preferences without any hints to the "Skip All Breakpoints" option. Adding messages explaining this should really be trivial but helpful.

Also see this question on Stackoverflow: http://stackoverflow.com/questions/3187805/eclipse-helios-ignores-breakpoints/3188282

Reproducible: Always

Steps to Reproduce:
1. Toggle "Skip All Breakpoints" in Breakpoints view
2. Check hover message of any breakpoint
3. Check preferences of any breakpoint
Comment 1 Curtis Windatt CLA 2010-07-07 14:41:21 EDT
The breakpoint icons in the ruler and breakpoints view should all get rendered with a slash through them when skip all breakpoints is enabled.  This is the same icon that is used in the breakpoints view and menu to toggle the option.

This bug can stay open as a explanation in the hover would be more helpful.  However, there are no plans to work on it.
Comment 2 Eclipse Genie CLA 2019-05-03 16:17:38 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.