Keresztfalvi Gabor <[EMAIL PROTECTED]> writes:
> Hmmm. With this new channel.c it's getting more wierd!
> The client disconnects, but the server aborts...
> Client sais:
> <snip>
> Sending EOF on channel 0
> Connection died, for reason 1.
> Sending CLOSE on channel 0
> write_buffer: Attempt to write data to closed buffer.
>
> Server sais:
> <snip>
> Taking channel 0 in use, (local 0).
> Garbage collecting while idle...
> Objects alive: 183, garbage collected: 309
> Child 7288 died with exit code 0.
> Receiving EOF on channel 0 (local 0)
> lshd: server_session.c:214: do_send_adjust: Assertion `session->err->read'
> failed.
> IOT trap/Abort
That's bad. Can you get a C backtrace (either by running lshd inside
gdb, or with the --enable-core option so that you get a core dump to
analyze)?
/Niels
