Guest User

Untitled

a guest
May 1st, 2018
146
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Lisp 1.90 KB | None | 0 0
  1. MAXIMA> (load "/usr/local/share/maxima/5.41.0/share/pdiff/pdiff.lisp")
  2.  
  3. ; file: /usr/local/share/maxima/5.41.0/share/pdiff/pdiff.lisp
  4. ; in: DEFUN PDIFF-GET-NUMBER-ARGS
  5. ;     (MAXIMA::MEMQ MAXIMA::F
  6. ;                   '(MAXIMA::%LOG MAXIMA::%GAMMA MAXIMA::%ERF MAXIMA::%SQRT
  7. ;                     MAXIMA::MABS))
  8. ;
  9. ; caught WARNING:
  10. ;   Compile-time package lock violation:
  11. ;     Lock on package SB-KERNEL violated when declaring *HANDLER-CLUSTERS* special
  12. ;     while in package MAXIMA.
  13. ;   See also:
  14. ;     The SBCL Manual, Node "Package Locks"
  15. ;
  16. ; caught ERROR:
  17. ;   Lock on package SB-KERNEL violated when declaring *HANDLER-CLUSTERS* special
  18. ;   while in package MAXIMA.
  19. ;   See also:
  20. ;     The SBCL Manual, Node "Package Locks"
  21. While evaluating the form starting at line 33, column 0
  22.  
  23. Maxima encountered a Lisp error:
  24.  
  25.    failed AVER: (NOT (SB-C::CTRAN-NEXT SB-C::CTRAN))
  26.  This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
  27.  corrupted by bad user code, e.g. by an undefined Lisp operation like
  28.  (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
  29.  Lisp code; or there might be a bug in the OS or hardware that SBCL is running
  30.  on.) If it seems to be a bug in SBCL itself, the maintainers would like to
  31.  know about it. Bug reports are welcome on the SBCL mailing lists, which you
  32.  can find at <http://sbcl.sourceforge.net/>.
  33.  
  34. Automatically continuing.
  35. To reenable the Lisp debugger set *debugger-hook* to nil.
  36.   of #P"/usr/local/share/maxima/5.41.0/share/pdiff/pdiff.lisp":;
  37.                                                                ; compilation unit aborted
  38.                                                                ;   caught 1 fatal ERROR condition
  39.                                                                ;   caught 1 ERROR condition
  40.                                                                ;   caught 1 WARNING condition
Add Comment
Please, Sign In to add comment