View difference between Paste ID: <a href="/1DaEjQBt">1DaEjQBt</a> and <a href="/post/view"></a>

View difference between Paste ID: 1DaEjQBt and

SHOW: | | - or go back to the newest paste.


; compiling (DEFUN SEND-EVENT ...)
; file: /tmp/yaourt-tmp-robal/aur-clx/pkg/usr/share/common-lisp/source/clx/requests.lisp
; in: DEFUN SEND-EVENT
;     (APPLY (SVREF XLIB::*EVENT-SEND-VECTOR* XLIB::INTERNAL-EVENT-CODE)
;            XLIB:DISPLAY XLIB::ARGS)
; --> MULTIPLE-VALUE-CALL 
; ==>
;   (SB-KERNEL:%COERCE-CALLABLE-TO-FUN
;    (SVREF XLIB::*EVENT-SEND-VECTOR* XLIB::INTERNAL-EVENT-CODE))
; 
; note: unable to
;   optimize
; because:
;   optimize away possible call to FDEFINITION at runtime

debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" RUNNING
                                             {AA95F01}>:
    failed AVER: (AND (NULL (TN-READS TN)) (NULL (TN-WRITES TN)))
  This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
  corrupted by bad user code, e.g. by an undefined Lisp operation like
  (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
  Lisp code; or there might be a bug in the OS or hardware that SBCL is running
  on.) If it seems to be a bug in SBCL itself, the maintainers would like to
  know about it. Bug reports are welcome on the SBCL mailing lists, which you
  can find at <http://sbcl.sourceforge.net/>.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [TRY-RECOMPILING] Try recompiling requests
  1: [RETRY          ] Retry compiling component ("clx" "requests").
  2: [ACCEPT         ] Continue, treating
                       compiling component ("clx" "requests") as having been
                       successful.
  3: [CONTINUE       ] Ignore runtime option --eval "(asdf:operate 'asdf:compile-op 'clx)".
  4: [ABORT          ] Skip rest of --eval and --load options.
  5:                   Skip to toplevel READ/EVAL/PRINT loop.
  6: [QUIT           ] Quit SBCL (calling #'QUIT, killing the process).

1	-
1	+	; compiling (DEFUN SEND-EVENT ...)
2		; file: /tmp/yaourt-tmp-robal/aur-clx/pkg/usr/share/common-lisp/source/clx/requests.lisp
3		; in: DEFUN SEND-EVENT
4		; (APPLY (SVREF XLIB::EVENT-SEND-VECTOR XLIB::INTERNAL-EVENT-CODE)
5		; XLIB:DISPLAY XLIB::ARGS)
6		; --> MULTIPLE-VALUE-CALL
7		; ==>
8		; (SB-KERNEL:%COERCE-CALLABLE-TO-FUN
9		; (SVREF XLIB::EVENT-SEND-VECTOR XLIB::INTERNAL-EVENT-CODE))
10		;
11		; note: unable to
12		; optimize
13		; because:
14		; optimize away possible call to FDEFINITION at runtime
15
16		debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" RUNNING
17		{AA95F01}>:
18		failed AVER: (AND (NULL (TN-READS TN)) (NULL (TN-WRITES TN)))
19		This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
20		corrupted by bad user code, e.g. by an undefined Lisp operation like
21		(FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
22		Lisp code; or there might be a bug in the OS or hardware that SBCL is running
23		on.) If it seems to be a bug in SBCL itself, the maintainers would like to
24		know about it. Bug reports are welcome on the SBCL mailing lists, which you
25		can find at <http://sbcl.sourceforge.net/>.
26
27		Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
28
29		restarts (invokable by number or by possibly-abbreviated name):
30		0: [TRY-RECOMPILING] Try recompiling requests
31		1: [RETRY ] Retry compiling component ("clx" "requests").
32		2: [ACCEPT ] Continue, treating
33		compiling component ("clx" "requests") as having been
34		successful.
35		3: [CONTINUE ] Ignore runtime option --eval "(asdf:operate 'asdf:compile-op 'clx)".
36		4: [ABORT ] Skip rest of --eval and --load options.
37		5: Skip to toplevel READ/EVAL/PRINT loop.
38		6: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).