Bug 273194 - Filtering the execution stack in Debug-View
Summary: Filtering the execution stack in Debug-View
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement with 7 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-22 02:56 EDT by Olaf Kaus CLA
Modified: 2014-11-23 08:45 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Kaus CLA 2009-04-22 02:56:22 EDT
The debug stack shows allways the whole execution stack. So every frameworkmethode call is listed too. For example every AOP-Aspect, IOC-call or reflection-call. 

It would be realy nice if I can filter some packages to clean up the view and I see only my business calls (filter: org.springframework.*, org.hibernate.*, ...)

What do you think?

Kind regards
Olaf K.
Comment 1 Mike Wilson CLA 2009-05-05 14:45:05 EDT
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
Comment 2 Nobody - feel free to take it CLA 2010-01-29 07:08:58 EST
It would make sense to connect this feature to the step filters, so that for displaying the stack as well as for stepping, the same filters are used.
This would really be helpful, since, as mentioned, frameworks as Spring introduce a lot of indirection and delegation that don't matter to the developer.

This is of special importance when debugging OSGi service invocations. Filtering the stack trace from OSGi packages would hide the fact, that method invocations traverse bundle borders using the OSGi service registry.