00:05:48 -!- segv [n=mb@72-255-20-161.client.stsn.net] has quit [Read error: 60 (Operation timed out)] 00:16:03 segv [n=mb@72-255-20-161.client.stsn.net] has joined #ccl 00:39:49 phf [n=phf@c-98-231-150-21.hsd1.md.comcast.net] has joined #ccl 01:16:00 -!- sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has quit [] 01:26:02 sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has joined #ccl 01:34:25 -!- segv [n=mb@72-255-20-161.client.stsn.net] has quit [Read error: 104 (Connection reset by peer)] 01:36:35 segv [n=mb@72-255-20-161.client.stsn.net] has joined #ccl 01:50:23 -!- segv [n=mb@72-255-20-161.client.stsn.net] has quit [Read error: 60 (Operation timed out)] 01:52:33 segv [n=mb@72-255-20-161.client.stsn.net] has joined #ccl 02:00:50 -!- phf [n=phf@c-98-231-150-21.hsd1.md.comcast.net] has quit ["Leaving..."] 02:04:34 -!- segv [n=mb@72-255-20-161.client.stsn.net] has quit [Read error: 145 (Connection timed out)] 02:52:33 bfulgham_ [n=brent@adsl-69-234-109-44.dsl.irvnca.pacbell.net] has joined #ccl 02:58:37 -!- mdc_mobile [n=mdc_mobi@ds9.entity.com] has quit [] 03:02:06 mdc_mobile [n=mdc_mobi@ds9.entity.com] has joined #ccl 03:23:42 -!- sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has quit [] 03:24:25 sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has joined #ccl 03:25:16 -!- sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has quit [Client Quit] 03:32:24 sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has joined #ccl 05:10:53 -!- mdc_mobile [n=mdc_mobi@ds9.entity.com] has quit [] 06:47:19 -!- bfulgham_ [n=brent@adsl-69-234-109-44.dsl.irvnca.pacbell.net] has quit [Read error: 110 (Connection timed out)] 08:32:52 -!- rme [n=rme@pool-70-105-87-66.chi.dsl-w.verizon.net] has quit [] 08:38:03 H4ns1 [n=Hans@p57BBA476.dip0.t-ipconnect.de] has joined #ccl 08:48:40 -!- H4ns [n=Hans@p57BBA349.dip0.t-ipconnect.de] has quit [Nick collision from services.] 08:48:43 -!- H4ns1 is now known as H4ns 13:45:41 mdc_mobile [n=mdc_mobi@ds9.entity.com] has joined #ccl 13:51:08 -!- sellout [n=greg@c-24-128-50-176.hsd1.ma.comcast.net] has quit [] 14:01:19 anRch [n=markmill@nmd.sbx07269.sauguma.wayport.net] has joined #ccl 14:37:25 sellout [n=greg@guest-fw.dc4.itasoftware.com] has joined #ccl 15:09:29 -!- anRch [n=markmill@nmd.sbx07269.sauguma.wayport.net] has quit [] 15:13:55 segv [n=mb@ita4fw1.itasoftware.com] has joined #ccl 15:32:17 milanj [n=milan@77.46.250.185] has joined #ccl 15:34:54 xristos [n=x@dns.suspicious.org] has joined #ccl 16:02:25 xristos pasted "ccl 1.2 crash" at http://paste.lisp.org/display/72347 16:03:14 any ideas as to where its crashing 16:03:42 my program spawns a lot of threads that do socket io 17:30:52 I would try these things: First, try it in trunk ccl; if that doesn't help try running under gdb and poke around (http://trac.clozure.com/openmcl/wiki/CclUnderGdb)to see if anything looks familiar; if that doesn't help, wait for gb to wake up... 17:39:17 how do i get a backtrace in ccl from error ? 17:42:46 Well, an error that gets you into the kernel debugger "while executing foreign code" generally cannot get you a backtrace. If you got into the kernel debugger while executing lisp code, 'b' would get a backtrace. If you got a regular lisp error, :b gets a backtrace. 17:45:01 not in the case of the kernel crash 17:45:04 just a normal error 17:45:16 and i want to print a stack trace 17:46:09 i mean not from the debugger, but programmatically from a handler 17:52:59 print-call-history 17:54:55 xristos annotated #72347 with "untitled" at http://paste.lisp.org/display/72347#1 17:55:08 thanks 18:39:58 rme [n=rme@pool-70-105-87-66.chi.dsl-w.verizon.net] has joined #ccl 19:04:08 xristos annotated #72347 with "untitled" at http://paste.lisp.org/display/72347#2 19:13:10 xristos: in this case, try typing "(:y 533)" and then type ":b" to see a backtrace. 19:19:30 Is Hunchentoot (sp?) invoved in this ? 19:33:38 no 19:34:07 i just spawn 80-100 threads 19:34:20 which do socket work 19:36:04 Is it possible for you to send me your code and a test case ? 19:37:34 i will, just making sure its not my fault 19:40:07 is threading considered stable on osx/amd64 ? 19:44:42 Well I'd consider it stable because I don;t run into any bugs and don't hear of any. It'd be foolish to say that that means that there provably can't be any bugs; I don't know what causes the problems that you're seeing. 21:21:39 sellout- [n=greg@guest-fw.dc4.itasoftware.com] has joined #ccl 21:22:09 -!- sellout [n=greg@guest-fw.dc4.itasoftware.com] has quit [Read error: 104 (Connection reset by peer)] 21:51:54 -!- sellout- is now known as sellout 22:10:52 -!- segv [n=mb@ita4fw1.itasoftware.com] has quit [] 22:23:05 -!- sellout [n=greg@guest-fw.dc4.itasoftware.com] has quit [] 23:36:18 segv [n=mb@72-255-42-154.client.stsn.net] has joined #ccl 23:56:47 -!- milanj [n=milan@77.46.250.185] has quit ["Leaving"]