Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343668 - Potential NPE in XtextValidator
Summary: Potential NPE in XtextValidator
Status: CLOSED WORKSFORME
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-22 16:19 EDT by Karsten Thoms CLA
Modified: 2017-09-19 17:05 EDT (History)
1 user (show)

See Also:

Attachments
Screenshot: Debugger (542.78 KB, image/png)
2011-04-22 16:19 EDT, Karsten Thoms CLA 		no flags Details
View All 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 Karsten Thoms CLA 2011-04-22 16:19:19 EDT 
Created attachment 193945 [details]
Screenshot: Debugger

I am just hitting a NPE when I did clean my projects. In XtextValidator#checkEnumLiteralIsUnique() the EnumLiteralDeclaration instances have null for their 'literal' reference. This may indicate another problem, but the validator should be aware of this situation. Same NPE happens in checkEnumLiteralIsValid(), checkGeneratedEnumIsValid().
Comment 1 Sven Efftinge CLA 2011-04-24 13:46:58 EDT 
NPEs are handled by the validation framework (see AbstractDeclarativeValidator)
Comment 2 Karsten Thoms CLA 2011-04-26 04:39:53 EDT 
Somehow OK, but I find better when I do not hit such a breakpoint except for my own code to debug.
Comment 3 Karsten Thoms CLA 2017-09-19 16:54:32 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 17:05:25 EDT 
Closing all bugs that were set to RESOLVED before Neon.0