JastAddJ lookupType

Bug #696847 reported by Jesper Öqvist on 2011-01-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LJRT
Status tracked in Newfrontend
Newfrontend
Medium
Jesper Öqvist

Bug Description

lookupType can cause the JastAddJ compiler to crash without a sufficient error message if a certain type is missing.

For example if java.lang.Iterable is missing and JastAddJ is compiling an enhanced for statement, it checks if the type of the argument is an iterable type. A direct lookup on java.lang.Iterable is made, and if java.lang.Iterable is missing then JastAddJ will crash with a null pointer exception.

Changed in ljrt:
status: New → Confirmed
importance: Undecided → High
milestone: none → 1.1
assignee: nobody → Jesper Öqvist (jesper-oqvist)
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers