• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

java.lang.VerifyError question

 
Chris Shepherd
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can any one interpret this error message for me?

According to the docs, a VerifyError msg is "Thrown when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem. "
Is there any way to track this down? I have been doing some major reworking of may code and posting much of it would probably just be confusing. If someone could explain what the "(ILJob ;) V)" means it might give me a clue what's wrong.
The line that calls the DataScrollWindow calls it like this:

there is of course a matching constructor : DataScrollWindow(int,Job). Job is a class of my own. An instance of Job (job) exists at the time of the call to create the DataScrollWindow.
Any help with this would be appreciated.
Thanks,
Chris
--**-- Edited to disable smiles in the post
[ October 14, 2002: Message edited by: Chris Shepherd ]
 
Blake Minghelli
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just recently experienced my first VerifyError. It happened when I was trying to upgrade to a newer version (1.16) of the jikes java compiler. When I tried the latest version (1.17) the problem went away. By no means am I an expert on compilers but it seems like jikes 1.16 created some invalid bytecode . From what I understand about VerifyErrors, they occur when the jvm is initializing classes before they can be used.
What compiler are you using? Has your compiler changed since the last time you compiled the classes?
By the way, that error scared me because I was worried about what other classes it screwed up so I wrote a program that goes through all of my class files and does a "Class.forName(...)". Using jikes 1.16, there were 4 classes that threw VerifyErrors.
Hope that helps.
 
Chris Shepherd
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Blake, I went back and checked out the compiler my environment uses. It's an incremental compiler(compiles as you write the code) that came with my environment(CodeGuide). I had the option to recompile everything with javac, so I did and it seemed to fix the issue. This is the first time I'v run across anything like this with this code environment, so I'm still going to use it. I'll just have to send them a note and let them know it happened.
Thanks for the lead. It saved me a whole lot of grief.
Chris
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic