Bug 240519 - Null pointer exception when openning a dialog for adding exception break point
Summary: Null pointer exception when openning a dialog for adding exception break point
Status: VERIFIED DUPLICATE of bug 211962
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows Vista
: P3 major (vote)
Target Milestone: 3.3.2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-11 13:35 EDT by Wallace Peng CLA
Modified: 2008-09-16 07:44 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wallace Peng CLA 2008-07-11 13:35:54 EDT
Build ID: M20071205-0800

Steps To Reproduce:
1. open up eclipse platform
2. adding exception break point
3. shows the NPE dialog. so cannot add break point for exception any more.


More information:
Comment 1 Remy Suen CLA 2008-07-11 18:27:44 EDT
Are there any exceptions in your log files? Please take a look at workspace/.metadata/.log.
Comment 2 Wallace Peng CLA 2008-07-11 21:51:36 EDT
Yes please see below.

!ENTRY org.eclipse.core.jobs 4 2 2008-07-11 10:27:24.333
!MESSAGE An internal error occurred during: "Items filtering".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.jdt.internal.core.search.JavaSearchScope.packageFragmentRoot(JavaSearchScope.java:589)
	at org.eclipse.jdt.internal.core.search.TypeNameMatchRequestorWrapper.createTypeFromJar(TypeNameMatchRequestorWrapper.java:124)
	at org.eclipse.jdt.internal.core.search.TypeNameMatchRequestorWrapper.acceptType(TypeNameMatchRequestorWrapper.java:108)
	at org.eclipse.jdt.internal.core.search.BasicSearchEngine$2.acceptIndexMatch(BasicSearchEngine.java:767)
	at org.eclipse.jdt.internal.core.search.matching.InternalSearchPattern.acceptMatch(InternalSearchPattern.java:45)
	at org.eclipse.jdt.internal.core.search.matching.InternalSearchPattern.findIndexMatches(InternalSearchPattern.java:89)
	at org.eclipse.jdt.internal.core.search.matching.MatchLocator.findIndexMatches(MatchLocator.java:325)
	at org.eclipse.jdt.internal.core.search.PatternSearchJob.search(PatternSearchJob.java:114)
	at org.eclipse.jdt.internal.core.search.PatternSearchJob.execute(PatternSearchJob.java:64)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:279)
	at org.eclipse.jdt.internal.core.search.BasicSearchEngine.searchAllTypeNames(BasicSearchEngine.java:778)
	at org.eclipse.jdt.core.search.SearchEngine.searchAllTypeNames(SearchEngine.java:781)
	at org.eclipse.jdt.internal.debug.ui.breakpoints.AddExceptionDialog.fillContentProvider(AddExceptionDialog.java:481)
	at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$FilterJob.filterContent(FilteredItemsSelectionDialog.java:2083)
	at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$FilterJob.internalRun(FilteredItemsSelectionDialog.java:2025)
	at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$FilterJob.doRun(FilteredItemsSelectionDialog.java:1997)
	at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$FilterJob.run(FilteredItemsSelectionDialog.java:1984)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Comment 3 Wallace Peng CLA 2008-07-11 21:57:56 EDT
BTW, I have a lot of projects (15 or so) in my workspace. I dont know if it is caused by some plugins installed on my machine. 
Comment 4 Dani Megert CLA 2008-07-14 02:58:36 EDT
>Build ID: M20071205-0800
Please either use R3.3.2 or R3.4.
Comment 5 Dani Megert CLA 2008-07-14 02:58:51 EDT

*** This bug has been marked as a duplicate of bug 211962 ***
Comment 6 David Audel CLA 2008-09-16 07:44:55 EDT
Verified for 3.5M2