This is the mail archive of the
mailing list for the Java project.
Re: Possible bytecode verifier issues
- From: Tom Tromey <tromey at redhat dot com>
- To: "Ranjit Mathew" <rmathew at hotmail dot com>
- Cc: "GCJ" <java at gcc dot gnu dot org>
- Date: 27 Feb 2003 22:33:51 -0700
- Subject: Re: Possible bytecode verifier issues
- References: <OE61B03WG57m3ovyeaZ00011333@hotmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Ranjit" == Ranjit Mathew <rmathew4lists at hotmail dot com> writes:
Ranjit> With 3.2, he used to get lots of "bad pc in
Ranjit> exception_table" errors which disappeared with 3.3,
Ranjit> but now he gets "warning: exception handler inside
Ranjit> code that is being protected" warnings.
Just ignore this warning.
Recent versions of javac generate bytecode like this. In 3.3 we
changed this from an error to a warning.
Ranjit> Is this is a known issue with GCJ or could it be
Ranjit> that his class bytecodes are really SNAFU-ed?
No, they are fine. This is a weird corner case. The archives have a
nice explanation from (who else?) Eric Blake.