Results 1 to 4 of 4
  1. #1
    EBamber is offline Member
    Join Date
    Apr 2014
    Posts
    30
    Rep Power
    0

    Default EXCEPTION_ACCESS_VIOLATION in JPL‏

    #A fatal error has been detected by the Java Runtime Environment:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d287e54, pid=6792, tid=8108
    #
    # JRE version: 7.0-b147
    # Java VM: Java HotSpot(TM) Client VM (21.0-b17 mixed mode, sharing windows-x86 )
    # Problematic frame:
    # C [libswipl.dll+0x7e54]
    #
    # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #
    # An error report file with more information is saved as:
    # C:\Users\User\Desktop\Uni\Year 2 Semester 2\GAPT1\GAPT\hs_err_pid6792.log
    #
    # If you would like to submit a bug report, please visit:
    # HotSpot Virtual Machine Error Reporting Page
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #
    Hi, I keep getting this error when trying to run a program using the JPL API (Using JRE 1.7, the latest version of SWI-PL, on a windows platform).
    I've checked the statistics of my KB and got this back:

    3.510 seconds cpu time for 3,904,891 inferences
    20,501 atoms, 5,781 functors, 4,776 predicates, 124 modules, 373,000 VM-codes

    Limit Allocated In use
    Local stack : 134,217,728 30,720 784 Bytes
    Global stack : 134,217,728 63,480 2,780 Bytes
    Trail stack : 134,217,728 31,740 1,184 Bytes

    35 garbage collections gained 1,032,584 bytes in 0.000 seconds.
    1 atom garbage collections gained 10,053 atoms in 0.000 seconds.
    Stack shifts: 2 local, 3 global, 3 trail in -0.000 seconds.
    1 threads, 0 finished threads used 0.000 seconds.
    true.

    so I doubt that the program would go outside of the stack - I use 1 query to consult the kb, and I use a second one and recycle it to query the kb like so:

    Java Code:
    public LanguageProcessor(String user) // this constructor initializes the class by giving value to the class variable, and loading the knowledge base
        {
        	
        	//new queries are created to act as prolog queries inside the JVM by using the following syntax
        	JPL.init();
        	Query q1 = new Query("consult", new Term [] {new Atom("GAPT.pl")});       
            System.out.println(q1.query() ?"Hello, " + user + "how may I help you?" : "App could not be loaded"); 
            // where the 1st parameter of the Query/2 constructor is the type of prolog query, and the 2nd parameter is an array of all the terms used
        }
    Java Code:
    for(int i = 0; i < npt.size(); i++)
            {
            	String[] z = npt.get(i).split(" ");
            	input.add(new ArrayList<String>());
            	for(int j=0;j<z.length;j++)
            	{input.get(i).add(z[j]);}
            	String S = "[";
            	for (int j = 0; j<input.get(i).size();j++)
            	{
            		S+=input.get(i).get(j) + ",";
            	}
            	S+= "]";
            	Query q2 = new Query("s(_)", new Term [] {new Atom(S), new Atom("[]")});
            	check.add(q2.query());
            }
    I also call the JPL.halt() method when I'm done with my KB, I don't close the queries because Eclipse isn't reading any Query.close() methods in the API.
    I've tried running one of the test classes provided, and I received the same error.
    Thanks for your time.
    I can post the full error report on request.

  2. #2
    gimbal2 is offline Just a guy
    Join Date
    Jun 2013
    Location
    Netherlands
    Posts
    4,104
    Rep Power
    6

    Default Re: EXCEPTION_ACCESS_VIOLATION in JPL‏

    I don't think you will get much help here, that's a native crash; in other words a crash in native code, not in a Java class. There is just no debugging those, at best you can take this to the developers of whatever API you're using.
    "Syntactic sugar causes cancer of the semicolon." -- Alan Perlis

  3. #3
    EBamber is offline Member
    Join Date
    Apr 2014
    Posts
    30
    Rep Power
    0

    Default Re: EXCEPTION_ACCESS_VIOLATION in JPL‏

    Quote Originally Posted by gimbal2 View Post
    I don't think you will get much help here, that's a native crash; in other words a crash in native code, not in a Java class. There is just no debugging those, at best you can take this to the developers of whatever API you're using.
    would it help if I reinstalled the JRE or used a different one?
    I came here with my problem because the developer of the API told me he's not much for java so he couldn't help me solve the problem

  4. #4
    gimbal2 is offline Just a guy
    Join Date
    Jun 2013
    Location
    Netherlands
    Posts
    4,104
    Rep Power
    6

    Default Re: EXCEPTION_ACCESS_VIOLATION in JPL‏

    Unless the crash happens in a standard Java DLL (a quick google suggests it is not), the answer is not likely.
    "Syntactic sugar causes cancer of the semicolon." -- Alan Perlis

Similar Threads

  1. Exception_access_violation
    By anushkavaze22 in forum Advanced Java
    Replies: 1
    Last Post: 04-24-2012, 05:19 PM
  2. EXCEPTION_ACCESS_VIOLATION on Windows 7 32 bit
    By xihad in forum Advanced Java
    Replies: 1
    Last Post: 04-02-2012, 09:38 AM
  3. Exception_access_violation
    By midlandmonkey in forum Java Servlet
    Replies: 1
    Last Post: 06-21-2011, 09:48 AM
  4. Exception_access_violation
    By Solarsonic in forum New To Java
    Replies: 5
    Last Post: 05-12-2011, 10:33 PM
  5. Exception_access_violation
    By naveen.panc in forum JavaServer Pages (JSP) and JSTL
    Replies: 3
    Last Post: 11-15-2008, 12:27 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •