Any ideas what might trigger cl-postgres (postmodern 1.14) coming to
its knees with the backtrace shown below? No error or condition
description is given - sbcl (1.0.28) just retires from active duty and
drops into the debugger with the ("bogus stack frame") indication. The
postgresql server (8.3) log doesn't have any indication of trouble at
the time cl-postgres seems to run into trouble. This seems to only
happen intermittently (every few thousand queries), irreproducibly
(doesn't seem to be associated with a specific query or anything along
those lines), and only when the postgresql server is being utilized by
several lisp instances concurrently.
Thanks in advance for any input/ideas/troubleshooting suggestions...
- Alan
...
32: ("bogus stack frame")
33: (SB-IMPL::SUB-SUB-SERVE-EVENT NIL NIL)
34: (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL)
35: (SB-SYS:WAIT-UNTIL-FD-USABLE 5 :INPUT NIL)
36: (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "a socket" {C265BA9}>)
37: (SB-IMPL::INPUT-UNSIGNED-8BIT-BYTE
#<SB-SYS:FD-STREAM for "a socket" {C265BA9}>
T
NIL)
38: (CL-POSTGRES::SKIP-BYTES #<unavailable argument> #<unavailable argument>)
39: (CL-POSTGRES::TRY-TO-SYNC #<SB-SYS:FD-STREAM for "a socket" {C265BA9}> T)
40: ((FLET #:CLEANUP-FUN-[FORM-FUN-[SEND-QUERY]389]390))[:CLEANUP]
41: (CL-POSTGRES::SEND-QUERY
#<unavailable argument>
#<unavailable argument>
#<unavailable argument>)
42: ((LABELS #:G161))
43: (SQLG::QUERY-CORE
"select program from programs where programskey = '192828' ;"
20
#<unused argument>)
