Bug 37999 - Illegal bytecode sequence
Summary: Illegal bytecode sequence
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.0 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2003-05-22 17:31 EDT by Jared Burns CLA
Modified: 2009-08-30 02:06 EDT (History)
1 user (show)

See Also:

Attachments
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 Jared Burns CLA 2003-05-22 17:31:22 EDT 
Build 20030520
After using the "Extract interface" refactoring on a class, I
right clicked on the class in the package explorer (planning to
move it to an internal package), when the following appeared in the
console from which I'd launched Eclipse. I'd been doing a lot of
refactoring, but nothing out of the ordinary.

Unhandled Exception
Reason:
Unhandled Exception
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

Unhandled exception caught in event loop.
Reason:
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

java.lang.NullPointerException
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

Unhandled exception caught in event loop.
Reason:
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified =
===============

java.lang.NullPointerException
Comment 1 Dirk Baeumer CLA 2003-05-23 09:58:57 EDT 
Jared, any steps or further hint. This message isn't printed by refactoring.
Which VM are you using ?
Comment 2 Jared Burns CLA 2003-05-23 10:28:31 EDT 
Afraid I don't have any more clues. I'm on JDK 1.4.1.
Comment 3 Jared Burns CLA 2003-05-23 12:33:28 EDT 
I just had it happen again when I was launching. The problem doesn't
appear related to refactoring.
Comment 4 Philipe Mulet CLA 2003-05-23 12:36:35 EDT 
Can you provide steps to reproduce ? Normal VM dumps on bytecode verification 
errors do not look as such.

Need source reproducing this issue with a normal VM launch.
Comment 5 Olivier Thomann CLA 2003-05-23 13:58:25 EDT 
Add CC
Comment 6 Jared Burns CLA 2003-05-23 14:08:04 EDT 
No steps to reproduce yet. Figured I'd open the report anyway, so we
have somewhere to track the issue if/when more information becomes available.
Comment 7 Philipe Mulet CLA 2003-05-26 05:08:08 EDT 
Can you reproduce it with a different JRE ? I am suspecting some VM bug.
Comment 8 Philipe Mulet CLA 2003-06-11 09:34:44 EDT 
Closing. Please reopen if you can provide steps to reproduce.
Comment 9 Philipe Mulet CLA 2003-06-11 11:38:15 EDT 
Actually tagging as waiting for more information
Comment 10 Philipe Mulet CLA 2003-06-12 06:21:36 EDT 
If more information is available, please reopen the problem for further 
consideration.
Comment 11 Philipe Mulet CLA 2003-09-19 05:49:18 EDT 
Closing since no activity in past 3 months.
Comment 12 Denis Roy CLA 2009-08-30 02:06:21 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.