armedbear-devel April 2015

armedbear-devel@common-lisp.net

54 participants
100 discussions

[armedbear-devel] Java 6+ Type-checking bytecode verifier compatible output: requirements analysis
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi all, At ECLM the other week, Alessio and I agreed to start working on a requirements analysis regarding the output required for the type-checking bytecode verifier. We know Mark wants to create an intermediate level code representation to address any issues that may arise. However, we want to assess requirements first and come up with a solution after that. That solution may or may not depend on such an intermediate representation. For now, we'd like to leave that undecided. So, what I learned that the type-checking bytecode verifier wants is that it can verify the state of the stack and of the locals for all bytecode instructions. In order to do so, it needs: 1. The "initial state" of stack and locals at the external entry points of a function (ie notably the start and any exception handlers) 2. Optional "state modifications" when locals start being used or when the flow from one instruction to another is broken (such as in case of (conditional) jumps) Apart from a different class file version number and an attribute to store this information in, that's it. More doesn't the verifier want to know. Is it your understanding as well that this is all that is required? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

[armedbear-devel] c++ library FreeLing from ABCL
by Alexandre Rademaker 08 Apr '15

08 Apr '15

I am trying to use a C++ library called FreeLing from ABCL (using the library JAVA API). I have just posted a question in http://stackoverflow.com/questions/17556912/calling-freeling-java-api-from- abcl. Does anyone know of any limitation of ABCL to deal with the System.load of Java? Best, Alexandre

3 7

[armedbear-devel] Bug: COND clauses must have a test
by Pascal J. Bourguignon 08 Apr '15

08 Apr '15

The syntax for COND is: cond {clause}* => result* clause::= (test-form form*) therefore (cond ()) should be a program-error, but abcl 1.0.1 returns NIL. -- __Pascal Bourguignon__ http://www.informatimago.com/

2 1

[armedbear-devel] Next steps on our way to usability
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi all, With support for CloserMOP now almost released (great job! Thanks Rudi, Pascal and everybody who helped out!), I'm looking forward to see how we can run more quicklisp packages. If you look at http://common-lisp.net/project/cl-test-grid/abcl/abcl-1-2-0-load-failures.h… and the load failures recently published for 1.2.0, you'll see that the root blockers now (apart from cl-glfw-opengl-core<http://cl-test-grid.appspot.com/blob?key=1fgcximsyj> which fails due to a missing dynamic library) portability libraries: uffi, iolib.base, kmrcl, acl-compat and metatilities. Seems we're looking for people who want to submit portability code to these projects! Bye, Erik.

2 2

[armedbear-devel] Some convenience functions
by Theam Yong Chew 08 Apr '15

08 Apr '15

Hi all, I've got a bunch of useful functions for general hacking with abcl. Hope they could be useful. Any suggestions on the best place for sending patches (if indeed they are useful enough). abcl contribs, slime contribs, or core abcl? Yong ;; javap seems to be bundled/more widely available compared to the defaults (defun disassemble-class-cmd (path) (with-accessors ((d pathname-directory) (n pathname-name)) (merge-pathnames path) (format nil "cd ~{/~a~}; javap -c ~a" (cdr d) n))) (defun disassemble-class (path) (ext:run-shell-command (disassemble-class-cmd path))) (setf system::*disassembler* #'disassemble-class-cmd) (in-package :swank) (defmethod menu-choices-for-presentation ((throwable java:java-exception)) "Java exception stack traces (different from Lisp stack traces) are also available." (list (list "printStackTrace" (lambda (choice object id) (declare (ignore choice id)) ;; TODO, print to an Emacs buffer instead (java:jcall "printStackTrace" *standard-output* (java:java-exception-cause object)))))) (in-package :swank-backend) ;; Not real frame local variables, but it at least exposes function ;; arguments for possible inspection (defimplementation frame-locals (index) (loop for id upfrom 0 for item in (java:jcall "toLispList" (nth-frame index)) collect (let () ;; ((id id) (item item)) (list :name "??" :id id :value item)))) (defimplementation frame-var-value (index id) (elt (java:jcall "toLispList" (nth-frame index)) id))

2 1

[armedbear-devel] ABCL 1.2.1 Release
by Mark Evenson 08 Apr '15

08 Apr '15

We think that [abcl-1.2.1][] represents the final release engineering work for the version available at ECLM 2013. A description of the [CHANGES] is included with the source. Upcoming in abcl-1.3.0: o per function call stack and memory exception handler in CL:COMPILE o further fixes in Quicklisp, q.v. [abcl-1.2.1]: http://abcl.org/releases/1.2.1 [CHANGES]: http://abcl.org/svn/tags/1.2.1/abcl/CHANGES

1 0

Re: [armedbear-devel] 20130823a Diffs for chemicalamba (Akka bridge in ABCL)
by Mark Evenson 08 Apr '15

08 Apr '15

On Aug 22, 2013, at 9:37 PM, ubikation _ <ubikation(a)gmail.com> wrote: > Hey Mark, > > I really appreciate your help but I am having trouble understand the diffs that you are sending me. I understand that HG is generating them but I am having trouble recreating your state. What tools do you recommend? I understand that creating a huge class isn't a good Java practice and I'm happy to break it up but it was hard for me to figure out exactly what goes where according to your diffs. […] For any software development, open or not, coming to terms with "diffs" is a basic skill that has no "right answer" for the tools one uses. A "diff" is a standardized format, used by a variety of tools including most IDEs these days. But in the beginning there was the command line, so the first tools you should come to terms with are diff(1) and patch(1): cmd$ [[[clone repo into "./chemicalambda"]]] cmd$ cd chemicalambda cmd$ patch -p 1 < file-that-contains-the-diff.diff The "-p 1" strips the top-level of the hierarchy, and then patch reads the contents of stdin for changes to make. One will see either success or error messages in applying the diff. Re-do until you get the results you want, then deal with the changes in your own version control ecology. What I like about hg is that one can just directly import a diff into the repo: cmd$ hg import file-that-contains-the-diff.diff but git certainly has similar functionality, somewhere. I avoided a comprehensive understanding diffs for many years, much to my own detriment.

1 0

[armedbear-devel] Unsubscribe
by Wayne Rogers 08 Apr '15

08 Apr '15

1 0

[armedbear-devel] bug: example java-to-lisp1 does not compile (ABCL 1.2.1)
by David Catteeuw 08 Apr '15

08 Apr '15

Hello, While experimenting with ABCL, i noticed that the example "java-to-lisp1" cannot be compiled using ABCL 1.2.1. It does compile using ABCL 1.1.1. The method "findPackage(String)" seems to have disappeared from "Packages" in the new release. java-to-lisp1$ javac -cp /Applications/Dev/abcl-1.1.1/abcl.jar:. *.java java-to-lisp1$ javac -cp /Applications/Dev/abcl-1.2.1/abcl.jar:. *.java MainAlternative.java:39: cannot find symbol symbol : method findPackage(java.lang.String) location: class org.armedbear.lisp.Packages Packages.findPackage("CL-USER"); ^ 1 error java-to-lisp1$ java version "1.6.0_51" Java(TM) SE Runtime Environment (build 1.6.0_51-b11-457-10M4509) Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-457, mixed mode) java-to-lisp1$ javac -version javac 1.6.0_51 java-to-lisp1$ Kind regards, david.

2 2

Re: [armedbear-devel] threads:interrupt-thread
by Carlos Ungil 08 Apr '15

08 Apr '15

Hello Erik, I don't know how to debug java processes but I have an intuition about why those threads are not interrupted: they're never waiting. See the example below: an interruption scheduled for the interpreter thread is only executed when I put the thread to sleep (and if the garbage collector runs in the meantime it's lost). The reason why I cared about being able to interrupt the main thread was to run finalizers from there, to avoid concurrency issues in a foreign library. In the end I implemented an alternative solution using locks so I'm not really concerned about this problem anymore. Regards, Carlos CL-USER(1): (let ((main (threads:current-thread))) (threads:make-thread (lambda () (threads:interrupt-thread main (lambda () (print "Hi there!")))))) #<THREAD {3AF6EA95}> CL-USER(2): (* 2 2) 4 CL-USER(3): (sleep 1) "Hi there!" NIL CL-USER(4): (let ((main (threads:current-thread))) (threads:make-thread (lambda () (threads:interrupt-thread main (lambda () (print "Hi there!")))))) #<THREAD {CE5A31A}> CL-USER(5): (gc) 462843184 CL-USER(6): (sleep 1) NIL On 06/09/2013, at 21:49, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi Carlos, > > > is there a reason why interrupt-thread doesn't seem to run the requested function in some cases? The following code tries to run a function in each existing thread (the variable *output* logs the calls that we try to run and the ones that are actually run). > > Looking at your code, there may be multiple causes for the strings not showing up in the output. Frst of all, there's a problem with concurrency in your code: pushing into the *output* variable across threads isn't thread safe. The other reason for the code not being executed could be a bug: the code "checks manually" whether the thread interrupt has been invoked and executes the function(s) handed over. Maybe these threads land in loops that do not check this condition. > > (defvar *output*) > > > > (defun test-run () > > (setf *output* nil) > > (threads:mapcar-threads > > (lambda (thread) > > (push (format nil "~A : calling" thread) *output*) > > (threads:interrupt-thread thread > > (lambda () > > (push (format nil "~A : running" thread) *output*)))))) > > > > (defun test-report () > > (format t "~{~A~%~}" (reverse *output*))) > > > > Running in the command line: > > [snip] > > > > > I can understand that the thread "TEST-RUN" that I create to run the function might disappear before it gets to run the function as requested, or maybe the reason is that a thread can't interrupt itself by design... But why doesn't the thread "interpreter" run the function? > > > > Running in slime there are many threads present, and most of them will respond as expected. But "TEST-RUN", "interpreter" and "reader-thread" won't. > > Can you interrupt the reader-thread and interpreter thread in a java debugging environment and tell me what the stack trace is when you send the signal that isn't being processed? Maybe the answer turns out to be really obvious. > Thanks! > > Bye, > > > Erik. >

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel April 2015