it's nothing urgent on my part, just as a data point that may help: i've updated the sbcl that runs dwim.hu from this (+ small changes):
commit abb03f939ada55bdc1856df5cc48815fd0dff69d
1.0.55: will be tagged as "sbcl-1.0.55"
to the current head (+ the same small changes):
2b29a7c2b236cfab1d4d06311e84414abba71b4c
Dec 21, 2012
and when i want to start the server it hangs quite early in filling method caches:
2012-12-22T04:51:53.228687+01:00: Starting up server, PID is 11740
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD "main thread" RUNNING {100C5710A3}>: Interactive interrupt at #x7FFFF7488BE7.
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Return from SB-UNIX:SIGINT.
1: [SAVE-CORE-AND-DIE] Save image to /tmp/sbcl.core and die
2: [ABORT ] Give up starting the image and quit the VM process with exit code 2
the behavior is very strange, because if i C-c it and ask for a backtrace, then i get some 4 frames, and then it hangs again. then if i C-c is again a couple of times, then i get some more frames. if i repeat, i can get a full backtrace incrementally.
the application is a saved executable core, and it installs signal handlers on C-c like this:
it's nothing urgent on my part, just as a data point that may help: i've updated the sbcl that runs dwim.hu from this (+ small changes):
commit abb03f939ada55b dc1856df5cc4881 5fd0dff69d
1.0.55: will be tagged as "sbcl-1.0.55"
to the current head (+ the same small changes):
2b29a7c2b236cfa b1d4d06311e8441 4abba71b4c
Dec 21, 2012
and when i want to start the server it hangs quite early in filling method caches:
2012-12- 22T04:51: 53.228687+ 01:00: Starting up server, PID is 11740 INTERACTIVE- INTERRUPT in thread #<THREAD "main thread" RUNNING {100C5710A3}>: Interactive interrupt at #x7FFFF7488BE7.
debugger invoked on a SB-SYS:
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly- abbreviated name):
0: [CONTINUE ] Return from SB-UNIX:SIGINT.
1: [SAVE-CORE-AND-DIE] Save image to /tmp/sbcl.core and die
2: [ABORT ] Give up starting the image and quit the VM process with exit code 2
("bogus stack frame")
0] back
0: ("bogus stack frame") :%%WAIT- FOR-MUTEX :%WAIT- FOR-MUTEX <SB-THREAD: MUTEX "World Lock" owner: #<SB-THREAD:THREAD "main thread" RUNNING {10001EA793}>> <SB-THREAD: THREAD "main thread" RUNNING {100C5710A3}> INTERRUPTS- BODY-465 :IN SB-THREAD: :CALL-WITH- RECURSIVE- LOCK)) :CALL-WITH- RECURSIVE- LOCK :WITH-RECURSIVE -LOCK-THUNK :IN SB-PCL: :CHECK- WRAPPER- VALIDITY) {7FFFF6FEF7EB}> <SB-THREAD: MUTEX "World Lock" owner: #<SB-THREAD:THREAD "main thread" RUNNING {10001EA793}>> :CHECK- WRAPPER- VALIDITY #<error printing a HU.DWIM. HOME:HOME- SERVER: #<SB-SYS: INTERACTIVE- INTERRUPT {100C892343}>>) :CACHE- MISS-VALUES <STANDARD- GENERIC- FUNCTION HU.DWIM. WEB-SERVER: :LISTEN- ENTRIES- OF (1)> INTERACTIVE- INTERRUPT {100C897103}>> SB-PCL::ACCESSOR) :INITIAL- DFUN <STANDARD- GENERIC- FUNCTION HU.DWIM. WEB-SERVER: :LISTEN- ENTRIES- OF (1)> INTERACTIVE- INTERRUPT {100C89B683}>>)
1: (SB-THREAD:
#<unavailable argument>
#<unavailable argument>
#<unavailable argument>
#<unavailable argument>
#<unavailable argument>)
2: (SB-THREAD:
#
#
NIL
NIL
NIL
NIL
NIL
NIL)
3: ((FLET #:WITHOUT-
4: (SB-THREAD:
#<CLOSURE (FLET SB-THREAD:
#
T
NIL)
5: (SB-PCL:
6: (SB-PCL:
#
(#<error printing a CONS: #<SB-SYS:
7: (SB-PCL:
#
(#<error printing a CONS: #<SB-SYS:
[...]
the behavior is very strange, because if i C-c it and ask for a backtrace, then i get some 4 frames, and then it hangs again. then if i C-c is again a couple of times, then i get some more frames. if i repeat, i can get a full backtrace incrementally.
the application is a saved executable core, and it installs signal handlers on C-c like this:
http:// dwim.hu/ darcsweb/ darcsweb. cgi?r=HEAD% 20hu.dwim. util;a= headblob; f=/source/ production. lisp#l228