Hi there,
No, this is not the usual asked question regarding tab completion ;-)
I am trying to get tab completion working with CLISP, but the native
Windows port (downloaded from sourceforge) doesn't support it. So I
compiled the sources for cygwin under Windows. Everything worked
fine, however the tab completion just crashes CLISP with a
segmentation fault and core dump :(
Is there anything I can do to get completion work?
TIA!
Chris
Hi Chris...,
> No, this is not the usual asked question regarding tab completion ;-) I
> am trying to get tab completion working with CLISP, but the native
> Windows port (downloaded from sourceforge) doesn't support it. So I
> compiled the sources for cygwin under Windows. Everything worked fine,
> however the tab completion just crashes CLISP with a segmentation fault
> and core dump :(
>
> Is there anything I can do to get completion work?
This may be the GCC issue. Try compiling with GCC 2.95.x or merely figure
out why GCC 3.2.x is causing the problem with Tab completion :-)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183796
http://clisp.cons.org/wanted.html#completion
Regards,
Adam
Hello!
Adam Warner <······@consulting.net.nz> wrote:
>[...]
>This may be the GCC issue. Try compiling with GCC 2.95.x or merely figure
>out why GCC 3.2.x is causing the problem with Tab completion :-)
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183796
>http://clisp.cons.org/wanted.html#completion
That could well be a gcc problem, so I can't really appreciate that,
according to the last comment on the cited Debian bug report, clisp
might *require* gcc3 soon.
I've heard of problems while using gcc 3.2.2's optimizer (specifically:
apache, which fails strangely when compiled with -O2 or -O3;
rdesktop, when compiled with -O3, at least).
>Regards,
>Adam
Kind regards,
Hannah.
> * In message <············@c3po.use.schlund.de>
> * On the subject of "Re: CLISP tab completion problem"
> * Sent on 29 Apr 2003 11:43:13 GMT
> * Honorable ······@schlund.de (Hannah Schroeter) writes:
>
> Adam Warner <······@consulting.net.nz> wrote:
> >[...]
>
> >This may be the GCC issue. Try compiling with GCC 2.95.x or merely figure
> >out why GCC 3.2.x is causing the problem with Tab completion :-)
<https://sourceforge.net/tracker/index.php?func=detail&aid=723097&group_id=1355&atid=101355>:
Looking at the assembly section for
pushSTACK(array);
var object encoding = O(foreign_encoding);
I can see that a single
addl $4, %ebx
is missing in between. It re-appears when I add some printf+
nobject_out(STACK_0) inbetween.
> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183796
> >http://clisp.cons.org/wanted.html#completion
>
> That could well be a gcc problem, so I can't really appreciate that,
> according to the last comment on the cited Debian bug report, clisp
> might *require* gcc3 soon.
CLISP C sources freely mix declarations and statements
(as permitted by C99).
Compilation with pre-C99 compilers
requires pre-processing that inserts braces.
E.g., the following foo.d file fragment:
{
...
foo();
var int counter;
...
}
is converted to foo.c:
{
...
foo();
{int counter;
...
}}
We did discuss ditching support for pre-C99 compilers.
This is not about to happen soon because MSC does not support C99.
(even assuming that GCC3 will be fixed - which may be a vain hope
because the bug has not been reported to them yet).
--
Sam Steingold (http://www.podval.org/~sds) running RedHat9 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
If you think big enough, you'll never have to do it.
> * In message <····························@posting.google.com>
> * On the subject of "CLISP tab completion problem"
> * Sent on 28 Apr 2003 13:45:47 -0700
> * Honorable ··············@web.de (Chris...) writes:
>
> compiled the sources for cygwin under Windows. Everything worked
> fine, however the tab completion just crashes CLISP with a
> segmentation fault and core dump :(
CVS head should work. please try it.
--
Sam Steingold (http://www.podval.org/~sds) running RedHat9 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
In C you can make mistakes, while in C++ you can also inherit them!