CC-ing ecl-list since this might look similar to problems that ecl git
currenty have with new slime.
You can see backtrace by attaching gdb to ecl process. You do something like:
pgrep ecl
gdb ~/bin/ecl ecl_pid
Right now I'm getting this backtrace while running hunchentoot-tests.
(gdb) bt
#0 0x
Yes, the problem was similar.
After updating ECL from git, it seems it behaves differently now. When
I try hunchentoot test it just waits and does nothing.
Regards,
Marko
___
usocket-devel mailing list
usocket-devel@common-lisp.net
http://common-lisp.n
Hi, Marko
I used latest USOCKET code on trunk and Hunchentoot 1.1.0 with your patch.
Every files compiled fined and I can start hunchentoot test server. But when I
tried to connect to it using a web browser, I got this error:
> (hunchentoot:start (make-instance 'hunchentoot:acceptor :port 4242)
Hi Chun Tian,
The platform is Ubuntu 9.04 x64. Here's the patch to hunchentoot to
make it compile with ecl. When I try to run hunchentoot tests or to
access any page I get different errors.
I don't know when to start looking, since I'm new to both usockets and
hunchentoot.
Regads,
Marko
On Fri,
Hi, Marko
What's your platform? If it's not MS Windows, please show your backtraces when
error happens.
Regards,
Chun Tian (binghe)
在 2010-2-12，01:24， Marko Kocić 写道：
> Hi all,
>
> what is the status of latest ECL support in usocket?
>
> By running tests it seems that some stuff is not supp
Hi all,
what is the status of latest ECL support in usocket?
By running tests it seems that some stuff is not supported yet.
I'm trying to get hunchentoot to run with ECL, managed to make it
compile hunchentoot with some patches, but when running it fails in
usocket:wait-for-input-internal.
If s
