Bug 37930 - [breakpoints] Unable to set breakpoints based on search results
Summary: [breakpoints] Unable to set breakpoints based on search results
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-05-21 11:41 EDT by Tim C CLA
Modified: 2007-05-23 11:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim C CLA 2003-05-21 11:41:49 EDT
The ability to set a breakpoint in vertical ruler (or otherwise) from the 
search view would be quite helpful.  Ideally I envision using either a right-
click menu option from within the search results view, or a search view toolbar 
option to set breakpoints to ALL search results.  The major usefulness would 
happen when using multiple highligted search results.  

I commonly come across cases where setting a break point to each line found 
after search results of a References type of search is necessary.  Thus, 
allowing traces back to the source of an intantiation.

More specifically this would allow one to search all references of the object 
type, set breaks to all those results, run the application to verify which 
references are hit for the scenario run.  

Additionally, instead of requiring the user to record each of these places that 
were hit for a particular scenario, an additional enhancement would be the 
ability to save the set of breakpoints encountered under some label/name 
(though I believe something similar to this last point already exists).  This 
would eliminate the need to manually remove those that were not encountered.
Comment 1 Darin Wright CLA 2004-03-01 16:42:49 EST
Deferred
Comment 2 Michael Rennie CLA 2007-05-23 11:04:26 EDT
reopening
Comment 3 Michael Rennie CLA 2007-05-23 11:04:53 EDT
marking as wontfix, although contributions are welcome