You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I rebuild CCL via (progn (ccl:rebuild-ccl :full t :verbose t) (ccl:quit)). Sometimes, at the end of the building process, the newest CCL master hangs with 0% CPU usage shown in top:
...
;Loading ./bin/ccl-export-syms.wx64fsl
;Loading ./l1-fasls/version.wx64fsl
;Loading H:/tools/msys64/home/emiherd/ccl/bin/jp-encode.wx64fsl
;Loading H:/tools/msys64/home/emiherd/ccl/bin/cn-encode.wx64fsl
;Loading H:/tools/msys64/home/emiherd/ccl/library/lispequ.wx64fsl
;Loading H:/tools/msys64/home/emiherd/ccl/library/sockets.wx64fsl
his file and in "ccl:l1;l1-files.lisp.newest"
Interrupting CCL with Ctrl+C simply kills the process instead of dropping into the debugger.
How should I start debugging this issue? Which Windows utility will show me what CCL hangs on? Is this a duplicate of #24?
(As a sidenote, there are some printing issues, possibly related to multithreading - the his file and in "ccl:l1;l1-files.lisp.newest" seen at the end of the log is a part of a line from much higher above.)
The text was updated successfully, but these errors were encountered:
I rebuild CCL via
(progn (ccl:rebuild-ccl :full t :verbose t) (ccl:quit))
. Sometimes, at the end of the building process, the newest CCL master hangs with 0% CPU usage shown intop
:Interrupting CCL with Ctrl+C simply kills the process instead of dropping into the debugger.
This issue was reproduced on Travis: https://travis-ci.com/phoe-trash/ccl/jobs/250105562
Attaching full compilation log.
How should I start debugging this issue? Which Windows utility will show me what CCL hangs on? Is this a duplicate of #24?
(As a sidenote, there are some printing issues, possibly related to multithreading - the
his file and in "ccl:l1;l1-files.lisp.newest"
seen at the end of the log is a part of a line from much higher above.)The text was updated successfully, but these errors were encountered: