From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25266 invoked by alias); 6 Jun 2008 20:38:35 -0000 Received: (qmail 25242 invoked by uid 22791); 6 Jun 2008 20:38:34 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jun 2008 20:38:01 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m56KbxMZ006865 for ; Fri, 6 Jun 2008 16:37:59 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m56KbwWR006044 for ; Fri, 6 Jun 2008 16:37:58 -0400 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m56Kbvwm013625 for ; Fri, 6 Jun 2008 16:37:58 -0400 Message-ID: <4849A002.5020402@redhat.com> Date: Fri, 06 Jun 2008 21:18:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: frysk Subject: Running frysk within an interpreter using JNI Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00085.txt.bz2 FYI, I've committed a prototype set of JNI bindings sufficient to run frysk's testsuite and, to a limited degree, run frysk utilities using an interpreted environment. So far I've got frysk-sys down to 10 failures (and elfutils up for two bugs :-). Once we've nailed down the remaining problems we'll be able to switch to these new bindings (we can also continue to compile natively) and flush the CNI code. In addition, we'll be able to switch to using SOLIBS and greatly reduce our executable foot print. However, in the intervening period we'll need to maintain both code bases. This shouldn't be hard though, by using JNIXX (a JNI binding generator), I've been able minimise the differences so that the new bindings look and behave similar to CNI. For the curious, and to make testing easier, I've also added two scripts to the build tree: Runner: a hack to make invoking an interpreter easier vis: $ ./Runner frysk.bindir.fhpd vm loaded (fhpd) load /bin/ls [0.0] Loaded executable file: /bin/ls (fhpd) JniRunner: JNI equivalent to TestRunner, for running the testsuite in tree: $ ./JniRunner frysk.testbed.TestForkFactory vm loaded Running testDetachedDaemon(frysk.testbed.TestForkFactory) ...PASS Running testAttachedDaemon(frysk.testbed.TestForkFactory) ...PASS Time: 0.45 OK (2 tests) Andrew