Re: [clisp-list] errors from socket-status

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...> [2008-12-24 12:37:07 -0800]:
>
> Sam Steingold writes:
>  > http://clisp.cons.org/impnotes/faq.html#faq-debug
> would've been worth while to mention that before

you have been using clisp for many many years.
maybe it would be a good idea for you to spend 5 minutes skimming over
the FAQ.

>  > also, do not forger to pass "CFLAGS=''" to configure to avoid the
>  > "-g -O2" idiocy.
> The #faq-debug suggests this isn't needed.

I now modifued makemake in the cvs head, it should not be.

>  > >   (gdb) break prepare_error 
>  > not needed if you follow the FAQ.
> I was wondering whether this would also set other break points that I
> would not want.

just disable them when you hit them.
"info break" in gdb.

>  > alas, if this conjecture were true, it would have been easy to
>  > reproduce: connect to a clisp running under gdb, step through to
>  > the code above, kill telnet before listen_char so that the
>  > connection is reset, then continue in gdb.  alas, no error is
>  > raised.
>
> Just killing telnet probably does not result in a reset.

what does?

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 8.10 (intrepid)
http://mideasttruth.com http://jihadwatch.org http://honestreporting.com
http://ffii.org http://iris.org.il http://thereligionofpeace.com
Daddy, what does "format disk c: complete" mean?