Bugzilla – Full Text Bug Listing
| Summary: | Potential NPE in XtextValidator | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Karsten Thoms <karsten.thoms> | ||||
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | P3 | CC: | sven.efftinge | ||||
| Version: | 2.0.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
NPEs are handled by the validation framework (see AbstractDeclarativeValidator) Somehow OK, but I find better when I do not hit such a breakpoint except for my own code to debug. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
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().