error: couldn't find or load main class org.overture.interpreter.debug.DBG Reader V2
While running the VDM-SL, I have the following error ( error: couldn't find or load main class org.overture.interpreter.debug.DBG Reader V2). I am working on windows 64bit, I am using Java 8, I don't have antivirus on my laptop and I have allowed the overture to run over the firewall.
Any help?
Sorry for the delay, but we've all been at the Overture workshop...
Can you review this issue, to see whether any of the ideas there help to solve your problem? https://github.com/overturetool/overture/issues/566
Many thanks for your reply, I have tried all the mentioned solutions but with no success.
Can you tell me what are the other possible reasons?
If none of these instructions helped then I'm not sure what's up. In which directory did you install Overture? Could this be permission related? Or perhaps something went wrong during the ZIP extraction process? Did you try to extract it to (say) the desktop folder?
It is difficult to guess what this might be, without more information, as Peter says. A few thoughts that might help:
- Do you have more than one version of Java installed on the machine?
- What does "java -version" report on a command line?
- Is it the JRE or a JDK that you have installed?
- Are you running the 64-bit Overture, or the 32-bit version on a 64-bit machine?
- Is this a test VDM-SL model or something more substantial?
- Do you have Overture running successfully elsewhere? What is different about that system?
- Has it ever worked, or did this start happening at some point?
- What is the precise version of Overture that you are running? If it is not the latest (2.7.2), can you try that please?
- Have any earlier versions of Overture worked on this machine?
- When do you see the error? When you attempt to "run" an evaluation? What are the settings in the launcher that you are invoking?
- Does everything else in Overture work - the editor, syntax and type checking while you enter a model? Does the PO generator work?
- Is there anything in the Eclipse "Error" view? If so, do these errors provide any stack trace information?
Sorry to ask so many questions, but it is difficult for us to guess what is happening otherwise! All we know is that some people do sometimes (very rarely) see this, and we don't (yet) know why, so if you could help us to pin it down, we would be grateful.
@GhadeerMobasher Did you ever manage to solve this?