| Summary: | WeavingHook does not handle when a class definition fails | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | benito1er <benito1er> |
| Component: | Weaving | Assignee: | Project Inbox <equinox.weaving-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | satyam.kandula, tjwatson |
| Version: | 3.7.1 | ||
| Target Milestone: | Juno | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
benito1er
I did a quick glance at the call stack and see that there is something wrong with the call of recordClassDefine() in ClasspathManager#defineClass(). There are chances that the argument passed could be null which seems incorrect. Moving it to Equinox team for investigation. The WeavingHook needs to protect in cases where the clazz is null. This can happen if there were exceptions defining the class or if the class was already defined by another thread. I suspect the issue here is that an LinkageException of some sort was thrown while defining the class. I had fixed this in bug 373397. Sorry I forgot about this original bug report. *** This bug has been marked as a duplicate of bug 373397 *** |