Bugzilla – Full Text Bug Listing
| Summary: | NPE in AbstractEditingModel.getInputStream | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Nicolas Bros <nicolas.bros> | ||||
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | curtis.windatt.public, karsten.thoms | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
version: Eclipse SDK Version: 3.7.0 Build id: I20110613-1736 Can you provide more details about when this happens for you? Looking at BuildInputContext (Line:51) it is possible to create a model for a null document, which is bad. However, I don't see when we would end up with a null document for an existing storage editor input. Sorry, I can't reproduce. It only happened once to me, and I don't remember exactly what I was doing right before the exception. It maybe happened when I copied a MANIFEST.MF to another project and then renamed it to "MANIFEST.MF.template". Maybe having two MANIFEST.MF at once confused PDE. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Issue just happened once 8 years ago. Closing. |
Created attachment 202218 [details] stacktrace I got a NPE trying to open a MANIFEST.MF (see attached stacktrace)