clisp-devel — closed list for developers and testers

[ clisp-Bugs-3545905 ] Hang with exemption

[SourceForge.net <no...@so...>]

Bugs item #3545905, was opened at 2012-07-19 08:29
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3545905&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: lmj ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Hang with exemption

Initial Comment:
The following RUN function eventually hangs for both the latest build (15589) and clisp-2.49.

(defstruct sema
  (count 0)
  (lock (mt:make-mutex))
  (cvar (mt:make-exemption)))

(defun inc-sema (sema)
  (mt:with-mutex-lock ((sema-lock sema))
    (incf (sema-count sema))
    (mt:exemption-signal (sema-cvar sema))))

(defun dec-sema (sema)
  (mt:with-mutex-lock ((sema-lock sema))
    (loop (cond ((plusp (sema-count sema))
                 (decf (sema-count sema))
                 (return))
                (t
                 (mt:exemption-wait
                  (sema-cvar sema) (sema-lock sema)))))))

(defun test (thread-count)
  (let ((from-threads (make-sema)))
    (loop repeat thread-count do
         (mt:make-thread
          (lambda () (inc-sema from-threads))
          :name "test"))
    (loop repeat thread-count do (dec-sema from-threads))))

(defun run ()
  (loop
     (test 16)
     (format t ".")
     (finish-output)))

Sometimes the outcome with the latest build is:

Internal error: statement in file "zthread.d", line 771 has been reached!!

The number of iterations until hanging tends to decrease as thread-count increases.

The following replacement for TEST should also be checked (it has exposed bugs in other CL implementations where the previous TEST did not).

(defun test (thread-count)
  (let ((from-threads (make-sema))
        (to-threads   (make-sema)))
    (loop repeat thread-count do
         (mt:make-thread
          (lambda ()
            (dec-sema to-threads)
            (inc-sema from-threads))
          :name "test"))
    (loop repeat thread-count do (inc-sema to-threads))
    (loop repeat thread-count do (dec-sema from-threads))))

Linux xi 3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux

gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) 

GNU CLISP 2.49+ (2010-07-17) (built 3551638844) (memory 3551639097)
Software: GNU C 4.6.3 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -pthread -DENABLE_UNICODE -DMULTITHREAD -DPOSIX_THREADS -DDYNAMIC_MODULES  libgnu.a  -lreadline -lncurses -ldl   -lsigsegv  
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.9
libreadline 6.2
Features: 
(REGEXP WILDCARD SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER LOGICAL-PATHNAMES MT SOCKETS GENERIC-STREAMS SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /home/jlawrence/usr/stow/clisp-dev/lib/clisp-2.49+/
User language: ENGLISH
Machine: I686 (I686) xi [127.0.1.1]

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3545905&group_id=1355

[ clisp-Bugs-3540345 ] Does not build under Cygwin

[SourceForge.net <no...@so...>]

Bugs item #3540345, was opened at 2012-07-04 20:02
Message generated for change (Comment added) made by dcolascione
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3540345&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Bruno Haible (haible)
Summary: Does not build under Cygwin

Initial Comment:
cd data && ln -s ../../doc/Symbol-Table.text .
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -I.  -Wl,--export-all-symbols spvw.o  spvwtabf.o  spvwtabs.o  spvwtabo.o  eval.o  control.o  encoding.o  pathname.o  stream.o  socket.o  io.o  funarg.o  array.o  hashtabl.o  list.o  package.o  record.o  weak.o  sequence.o  charstrg.o  debug.o  error.o  misc.o  time.o  predtype.o  symbol.o  lisparit.o  i18n.o  foreign.o  unixaux.o  built.o  ari80386.o modules.o -lintl -lreadline -lncurses -lavcall -lcallback -liconv -lsigsegv libgnu_cl.a -o lisp.exe
./lisp.exe -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp  -x \'(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)\'
  i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
  I I I I I I I      8     8   8           8     8     o  8    8
  I  \\ `+\' /  I      8         8           8     8        8    8
   \\  `-+-\'  /       8         8           8      ooooo   8oooo
    `-__|__-\'        8         8           8           8  8
        |            8     o   8           8     o     8  8
  ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8

Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/>

Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2010

Type :h and hit Enter for context help.

*** - handle_fault error2 ! address = 0x66683a70 not in [0x99a80000,0x99a80000) !
SIGSEGV cannot be cured. Fault address = 0x66683a70.
GC count: 1
Space collected by GC: 0 0
Run time: 0 31000
Real time: 0 837824
GC time: 0 0
Permanently allocated: 90560 bytes.
Currently in use: 354516 bytes.
Free space: 169772 bytes.
Makefile:1437: recipe for target `interpreted.mem\' failed


----------------------------------------------------------------------

Comment By: Daniel Colascione (dcolascione)
Date: 2012-07-12 17:19

Message:
The real problem here is actually that clisp isn't 4GB-clean. In my Cygwin
configuration, I load code above the 2GB mark (since I'm actually running
on a 64-bit system). clisp can't handle these pointers with the high bit
set, and it balks.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3540345&group_id=1355

[ clisp-Bugs-3540345 ] Does not build under Cygwin

[SourceForge.net <no...@so...>]

Bugs item #3540345, was opened at 2012-07-04 20:02
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3540345&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Bruno Haible (haible)
Summary: Does not build under Cygwin

Initial Comment:
cd data && ln -s ../../doc/Symbol-Table.text .
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -I.  -Wl,--export-all-symbols spvw.o  spvwtabf.o  spvwtabs.o  spvwtabo.o  eval.o  control.o  encoding.o  pathname.o  stream.o  socket.o  io.o  funarg.o  array.o  hashtabl.o  list.o  package.o  record.o  weak.o  sequence.o  charstrg.o  debug.o  error.o  misc.o  time.o  predtype.o  symbol.o  lisparit.o  i18n.o  foreign.o  unixaux.o  built.o  ari80386.o modules.o -lintl -lreadline -lncurses -lavcall -lcallback -liconv -lsigsegv libgnu_cl.a -o lisp.exe
./lisp.exe -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp  -x \'(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)\'
  i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
  I I I I I I I      8     8   8           8     8     o  8    8
  I  \\ `+\' /  I      8         8           8     8        8    8
   \\  `-+-\'  /       8         8           8      ooooo   8oooo
    `-__|__-\'        8         8           8           8  8
        |            8     o   8           8     o     8  8
  ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8

Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/>

Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2010

Type :h and hit Enter for context help.

*** - handle_fault error2 ! address = 0x66683a70 not in [0x99a80000,0x99a80000) !
SIGSEGV cannot be cured. Fault address = 0x66683a70.
GC count: 1
Space collected by GC: 0 0
Run time: 0 31000
Real time: 0 837824
GC time: 0 0
Permanently allocated: 90560 bytes.
Currently in use: 354516 bytes.
Free space: 169772 bytes.
Makefile:1437: recipe for target `interpreted.mem\' failed


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3540345&group_id=1355

Re: terminating clisp: clisp.exe vs lisp.exe

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

Hi,

> * Anton Vodonosov <nibqbabfbi@lnaqrk.eh> [2012-06-29 03:05:10 +0400]:
>
>> http://clisp.org/impnotes/faq.html#faq-fine
>
> Not that I am stingy for zorkmids, but as it's a kind
> of penalty, I should defend myself.

it's a joke, not a penalty.

> 08.06.2012, 06:20, "Sam Steingold" <sd...@gn...>:
>>>  * Anton Vodonosov <nibqbabfbi@lnaqrk.eh> [2012-06-08 01:55:03 +0400]:
>>>
>>>  It's not trivial to even get process id of lisp.exe.
>>
>> http://clisp.org/impnotes/syscalls.html#processes
>
> Of course I've read the process functions including getpid,
> but the difficulty is that I need to get ID of a grandchild
> of my program: myprogram -> clisp.exe -> lisp.exe

you can tell lisp.exe to write a pid file (if you can control which lisp
code it executes).


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://jihadwatch.org http://truepeace.org
http://palestinefacts.org http://thereligionofpeace.com http://ffii.org
The only substitute for good manners is fast reflexes.

Re: terminating clisp: clisp.exe vs lisp.exe

[Anton V. <avo...@ya...>]

Hello.

Sam, Pascal, thanks for the responses.

(I use different solution though, because the answers
not exactly apply to my situations, where on windows
lisp.exe is a granchild of my program process).

08.06.2012, 06:20, "Sam Steingold" <sd...@gn...>:
> PS. You now owe me 3 zorkmids. :-)
> http://clisp.org/impnotes/faq.html#faq-fine

Not that I am stingy for zorkmids, but as it's a kind
of penalty, I should defend myself.

08.06.2012, 06:20, "Sam Steingold" <sd...@gn...>:
> Hi,
>
>>  * Anton Vodonosov <nibqbabfbi@lnaqrk.eh> [2012-06-08 01:55:03 +0400]:
>>
>>  It's not trivial to even get process id of lisp.exe.
>
> http://clisp.org/impnotes/syscalls.html#processes

Of course I've read the process functions including getpid,
but the difficulty is that I need to get ID of a grandchild
of my program: myprogram -> clisp.exe -> lisp.exe

>
>>  What are my options to reliable kill started CLISP?
>
> killall -v lisp.exe
>
>>  Is it possible to start CLISP in a way that it consists only of one process?
>
> http://clisp.org/impnotes/image.html
> (saveinitmem ... :executable t)
>

No, this doesn't apply to me, because I do not control the clisp executable,
it's the user of my program configures the path to clisp executable.
And I can't require him to rebuild the executable.
 
>>  I am curious btw, what is the role of CLISP separation into lisp.exe
>>  and clisp.exe?
>
> http://clisp.org/impnotes/clisp.html#opt-link-set
> $ clisp -K base
> and
> $ clisp -K full
> start different lisp.exe files.

Of course I've found the chapter about clisp command line parameters
before asking the question. But it's long, so I didn't understood it completely,
I thought it only changes parameters passed to lisp.exe, but not choses
different lisp.exe

So, I agree to one zorkmid.
 
This zorkmund may be used to have me answering 1 technical question.

BTW, this kind of currency may be used in http://villages.cc - if you were registered
there I could transfer it to your account.

Best regards,
- Anton

Re: &key and how it's used

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

> * Yves S. Garret <lbhefheebtngrtbq@tznvy.pbz> [2012-06-17 14:20:13 -0400]:
>>
>  1) how *db* is accessed, that's where all the data is held and

(defun select (selector-fn)
  (remove-if-not selector-fn *db*))
 
(defun where (&key title artist rating (ripped nil ripped-p))
  #'(lambda (cd)
    (and
      (if title    (equal (getf cd :title)  title)  t) 
      (if artist   (equal (getf cd :artist) artist) t)
      (if rating   (equal (getf cd :rating) rating) t)
      (if ripped-p (equal (getf cd :ripped) ripped) t))))

SELECT returns elements of *DB* which satisfy SELECTOR-FN
WHERE returns a function which __APPARENTLY__ can be used as an argument
to SELECT.
e.g.,
(select (where :title "foo"))
will return the objects with the given title.


> 2) what the heck is &key?

a lambda list keyword.
http://www.lispworks.com/documentation/HyperSpec/Body/03_da.htm

it is a way to pass optional arguments to functions in a position
independent way.
e.g.:

(defun foo (&key (a 1) (b 2) (c 3))
  (list a b c))

(foo :b 10) => (1 10 3)
(foo :a 4 :c 5) => (4 2 5)
(foo :c 5 :a 4) => (4 2 5)

> If I'm missing something absurdly obvious, please feel free to point it out.

You might get a more detailed and informative reply to such a general
Lisp question on the comp.lang.lisp newsgroup.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://jihadwatch.org http://openvotingconsortium.org
http://iris.org.il http://palestinefacts.org http://mideasttruth.com
Democrats, get out of my wallet! Republicans, get out of my bedroom!

Re: &key and how it's used

[Yves S. G. <you...@gm...>]

Odd.  I've asked questions here before and got answers.  If I'm wrong, then
I will re-ask the question in the appropriate location.

Thanks for the heads up.

On Sun, Jun 17, 2012 at 3:08 PM, Pascal J. Bourguignon <
pj...@in...> wrote:

> "Yves S. Garret" <you...@gm...> writes:
>
> > Hi all,
> >
> >    I'm reading this chapter of gigamonkeys.
> >
> > http://www.gigamonkeys.com/book/practical-a-simple-database.html
> >
> > 2/3 down the page, I see the following methods:
> >
> > http://bin.cakephp.org/view/1169646936
> >
> > Now, where I'm drawing a complete and utter blank is 1) how *db* is
> > accessed, that's where all the data is held and 2) what the heck is
> > &key?
> >
> > If I'm missing something absurdly obvious, please feel free to point it
> out.
> >
>
> This is not the right place to ask that.
>
>
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>
>    This mailing list is for the developers of the CLISP implementation
>    of ANSI Common Lisp.  It is the proper forum for enhancement
>    requests, design discussions, source code patches, pre-release
>    announcements, etc. and also for those support questions which are
>    not appropriate for the users' list.
>
>
> https://lists.sourceforge.net/lists/listinfo/clisp-list
>
>    This mailing list is for users of the CLISP implementation of Common
>    Lisp by Bruno Haible and Michael Stoll. It is the proper forum for
>    questions about CLISP and also bug reports, compatibility issues,
>    problems of CLISP on specific platforms, enhancement of CLISP,
>    miscellaneous comments, etc.
>
> Stretching it, your question could enter the "miscellaneous comments"
> category, but since it really has nothing to do with clisp specifically,
> but more with Common Lisp in general, you should be asking it on:
> news://comp.lang.lisp
>
>
> &key is described in chapter "5. Functions" of "Practical Common Lisp".
> Lambda Lists are explained in section "3.4 Lambda Lists" of CLHS.
>
> --
> __Pascal Bourguignon__                     http://www.informatimago.com/
> A bad day in () is better than a good day in {}.
>

Re: &key and how it's used

[Pascal J. B. <pj...@in...>]

"Yves S. Garret" <you...@gm...> writes:

> Hi all,
>
>    I'm reading this chapter of gigamonkeys.
>
> http://www.gigamonkeys.com/book/practical-a-simple-database.html
>
> 2/3 down the page, I see the following methods:
>
> http://bin.cakephp.org/view/1169646936
>
> Now, where I'm drawing a complete and utter blank is 1) how *db* is
> accessed, that's where all the data is held and 2) what the heck is
> &key?
>
> If I'm missing something absurdly obvious, please feel free to point it out.
>

This is not the right place to ask that.


https://lists.sourceforge.net/lists/listinfo/clisp-devel

    This mailing list is for the developers of the CLISP implementation
    of ANSI Common Lisp.  It is the proper forum for enhancement
    requests, design discussions, source code patches, pre-release
    announcements, etc. and also for those support questions which are
    not appropriate for the users' list. 


https://lists.sourceforge.net/lists/listinfo/clisp-list

    This mailing list is for users of the CLISP implementation of Common
    Lisp by Bruno Haible and Michael Stoll. It is the proper forum for
    questions about CLISP and also bug reports, compatibility issues,
    problems of CLISP on specific platforms, enhancement of CLISP,
    miscellaneous comments, etc. 

Stretching it, your question could enter the "miscellaneous comments"
category, but since it really has nothing to do with clisp specifically,
but more with Common Lisp in general, you should be asking it on:
news://comp.lang.lisp


&key is described in chapter "5. Functions" of "Practical Common Lisp".
Lambda Lists are explained in section "3.4 Lambda Lists" of CLHS.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

&key and how it's used

[Yves S. G. <you...@gm...>]

Hi all,

   I'm reading this chapter of gigamonkeys.

http://www.gigamonkeys.com/book/practical-a-simple-database.html

2/3 down the page, I see the following methods:

http://bin.cakephp.org/view/1169646936

Now, where I'm drawing a complete and utter blank is 1) how *db* is
accessed, that's where all the data is held and 2) what the heck is &key?

If I'm missing something absurdly obvious, please feel free to point it out.

[ clisp-Bugs-3535519 ] Pressing Delete key at REPL strange characters.

[SourceForge.net <no...@so...>]

Bugs item #3535519, was opened at 2012-06-15 10:11
Message generated for change (Settings changed) made by aaronrdev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3535519&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
>Priority: 1
Private: No
Submitted By: Aaron Robson (aaronrdev)
Assigned to: Bruno Haible (haible)
Summary: Pressing Delete key at REPL strange characters.

Initial Comment:
Pressing the delete key causes the following characters to be inserted 'àS' (without quotes). Similar key sequences replace other keystrokes (home, end, page up, page down and most of the function keys (F1 to F12)). This does not happen in other command-line applications I use (Python's REPL for example).

Using version 2.49 on Windows 7 (64 bit) ("clisp-2.49-win32-mingw-big.exe" from 
"sourceforge.net/projects/clisp/").

The results of "clisp --version" are as follows:
GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by [150.0.0.63])
Software: GNU C 3.4.5 (mingw-vista special r3) 
gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -D_WIN32 -DENABLE_UNICODE -I/usr/local/include -DDYNAMIC_FFI -I. -L/usr/local/lib  -lintl /usr/local/lib/libreadline.dll.a -L/usr/local/lib -ltermcap /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a -luser32 -lws2_32 -lole32 -loleaut32 -luuid -liconv -L/usr/local/lib -lsigsegv libgnu_cl.a 
SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libiconv 1.13
libreadline 6.0
Features: 
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS
 LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 WIN32)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: C:\Program Files (x86)\clisp-2.49\
User language: ENGLISH
Machine: PC/386 (PC/@86) Eleanore-PC [192.168.0.42]


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3535519&group_id=1355

[ clisp-Bugs-3535519 ] Pressing Delete key at REPL strange characters.

[SourceForge.net <no...@so...>]

Bugs item #3535519, was opened at 2012-06-15 10:11
Message generated for change (Tracker Item Submitted) made by aaronrdev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3535519&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Aaron Robson (aaronrdev)
Assigned to: Bruno Haible (haible)
Summary: Pressing Delete key at REPL strange characters.

Initial Comment:
Pressing the delete key causes the following characters to be inserted 'àS' (without quotes). Similar key sequences replace other keystrokes (home, end, page up, page down and most of the function keys (F1 to F12)). This does not happen in other command-line applications I use (Python's REPL for example).

Using version 2.49 on Windows 7 (64 bit) ("clisp-2.49-win32-mingw-big.exe" from 
"sourceforge.net/projects/clisp/").

The results of "clisp --version" are as follows:
GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by [150.0.0.63])
Software: GNU C 3.4.5 (mingw-vista special r3) 
gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -D_WIN32 -DENABLE_UNICODE -I/usr/local/include -DDYNAMIC_FFI -I. -L/usr/local/lib  -lintl /usr/local/lib/libreadline.dll.a -L/usr/local/lib -ltermcap /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a -luser32 -lws2_32 -lole32 -loleaut32 -luuid -liconv -L/usr/local/lib -lsigsegv libgnu_cl.a 
SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libiconv 1.13
libreadline 6.0
Features: 
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS
 LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 WIN32)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: C:\Program Files (x86)\clisp-2.49\
User language: ENGLISH
Machine: PC/386 (PC/@86) Eleanore-PC [192.168.0.42]


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3535519&group_id=1355

digits_need

[Hopsing K <hop...@gm...>]

I wonder weather intprint.d:digits_need() doesnt return
a value too big. Shouldnt it be:

diff -Naur clisp-2.49/src/intprint.d.ori clisp-2.49/src/intprint.d
--- clisp-2.49/src/intprint.d.ori       2012-06-12 13:40:17.000000000 +0200
+++ clisp-2.49/src/intprint.d   2012-06-12 13:40:45.000000000 +0200
@@ -125,7 +125,7 @@
   local uintL digits_need (uintC len, uintWL base)
   {
     # 1+ceiling(len * intDsize*log(2)/log(base)) Bytes oder etwas mehr
-    var uintL need = 1+floor(len,1024/intDsize); # >
ceiling(len*intDsize/1024) >= 0
+    var uintL need = len; # > ceiling(len*intDsize/1024) >= 0
     switch (base) { # need mit ceiling(1024*log(2)/log(base))
multiplizieren:
       case 2: need = 1024*need; break;
       case 3: need = 647*need; break;
@@ -165,6 +165,7 @@
       default: NOTREACHED;
     }
     # Nun gilt need >= len*intDsize*log(2)/log(base).
+    need = floor(need,1024/intDsize);
     need += 1; # Platzbedarf in Bytes
     return need;
   }


=> The floor() at the end...

Re: terminating clisp: clisp.exe vs lisp.exe

[Pascal J. B. <pj...@in...>]

Sam Steingold <sd...@gn...> writes:

>> * Pascal J. Bourguignon <cwo@vasbezngvzntb.pbz> [2012-06-08 12:58:38 +0200]:
>>
>> Perhaps it would be a good idea to remove the call to fork() from the
>> clisp driver?
>
> there is no fork() there.
> unix uses execv(), windows uses CreateProcess().

Indeed.  The OP report is bogus.


Anton Vodonosov <avo...@ya...> writes:

> Hello.
>
> My program starts clisp as a child process to do some work.
> Sometimes this work may hang.
>
> In this case I would like to kill the child lisp process.
>
> clisp.exe starts another process, lisp.exe which, as I understand,
> preforms all the job.
>
> It's not trivial to even get process id of lisp.exe.

It is trivial to get the process id of a child process.  You just get it
as result of fork(2) (or CreateProcess()).  In bash(2), this child
process PID is returned by the special variable $!:

    clisp -norc -q -ansi \
        -x '(format t "~%clisp pid=~A~2%" (process-id))' & \
        echo "bash pid=$!"


> What are my options to reliable kill started CLISP?

Memorize the child PID, and use it to send a signal.


> Is it possible to start CLISP in a way that it consists only of one process?

It consists only of one process.




-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: terminating clisp: clisp.exe vs lisp.exe

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

> * Pascal J. Bourguignon <cwo@vasbezngvzntb.pbz> [2012-06-08 12:58:38 +0200]:
>
> Perhaps it would be a good idea to remove the call to fork() from the
> clisp driver?

there is no fork() there.
unix uses execv(), windows uses CreateProcess().

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://thereligionofpeace.com http://mideasttruth.com
http://iris.org.il http://ffii.org http://www.memritv.org http://truepeace.org
Those who don't know lisp are destined to reinvent it, poorly.

Re: terminating clisp: clisp.exe vs lisp.exe

[Pascal J. B. <pj...@in...>]

Anton Vodonosov <avo...@ya...> writes:

> Hello.
>
> My program starts clisp as a child process to do some work.
> Sometimes this work may hang.
>
> In this case I would like to kill the child lisp process.
>
> clisp.exe starts another process, lisp.exe which, as I understand,
> preforms all the job.
>
> It's not trivial to even get process id of lisp.exe.
>
> What are my options to reliable kill started CLISP?

killall will kill ALL your clisp processes, not only the one you want to
kill.

Given the current state of affair, your best bet is to open a pipe
between the parent process and the clisp process, and use it to provoke
a killing sigchld


> Is it possible to start CLISP in a way that it consists only of one process?

You can also run lisp.exe directly.  You must be careful with the options.



Perhaps it would be a good idea to remove the call to fork() from the
clisp driver?

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: terminating clisp: clisp.exe vs lisp.exe

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

Hi,

> * Anton Vodonosov <nibqbabfbi@lnaqrk.eh> [2012-06-08 01:55:03 +0400]:
>
> It's not trivial to even get process id of lisp.exe.

http://clisp.org/impnotes/syscalls.html#processes

> What are my options to reliable kill started CLISP?

killall -v lisp.exe

> Is it possible to start CLISP in a way that it consists only of one process?

http://clisp.org/impnotes/image.html
(saveinitmem ... :executable t)

> I am curious btw, what is the role of CLISP separation into lisp.exe
> and clisp.exe?

http://clisp.org/impnotes/clisp.html#opt-link-set
$ clisp -K base
and 
$ clisp -K full
start different lisp.exe files.

PS. You now owe me 3 zorkmids. :-)
http://clisp.org/impnotes/faq.html#faq-fine

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://jihadwatch.org http://camera.org
http://honestreporting.com http://www.PetitionOnline.com/tap12009/
There are many reasons not to use Linux - but no good ones.

terminating clisp: clisp.exe vs lisp.exe

[Anton V. <avo...@ya...>]

Hello.

My program starts clisp as a child process to do some work.
Sometimes this work may hang.

In this case I would like to kill the child lisp process.

clisp.exe starts another process, lisp.exe which, as I understand,
preforms all the job.

It's not trivial to even get process id of lisp.exe.

What are my options to reliable kill started CLISP?
Is it possible to start CLISP in a way that it consists only of one process?

I am curious btw, what is the role of CLISP separation into lisp.exe and
clisp.exe?

Best regards,
Anton

terminating clisp: clisp.exe vs lisp.exe

[Anton V. <avo...@ya...>]

Hello.

My program starts clisp as a child process to do some work. 
Sometimes this work may hang.

In this case I would like to kill the child lisp process.

clisp.exe starts another process, lisp.exe which, as I understand,
preforms all the job. 

It's not trivial to even get process id of lisp.exe.

What are my options to reliable kill started

Fwd: What happened when I changed directories?

[Yves S. G. <you...@gm...>]

First of all.  Thank you all for pointing out my silly mistake.  Late in
the day that I hacking that and I'm already kicking myself :-) .  I thought
it was an issue with clisp.

Second of all, I don't know why, but I never got any of your e-mails, only
the digest.  Going to look at my settings.

---------- Forwarded message ----------
From: Yves S. Garret <you...@gm...>
Date: Thu, May 31, 2012 at 9:14 PM
Subject: What happened when I changed directories?
To: clisp-devel <cli...@li...>


Hi guys.  I changed directories in clisp with (ext:cd "path/to/file") and
got this... could some please explain why I got this error and how could I
avoid it?

http://bin.cakephp.org/view/209161709

The command on line 7 shows that I got to the desired location, so the path
is valid (I suspected that I had fat-fingered the path and hence the error,
until I found out it switched correctly).

Re: What happened when I changed directories?

[Pascal J. B. <pj...@in...>]

Raymond Toy <toy...@gm...> writes:

> On 5/31/12 6:14 PM, Yves S. Garret wrote:
>> Hi guys.  I changed directories in clisp with (ext:cd "path/to/file")
>> and got this... could some please explain why I got this error and how
>> could I avoid it?
>>
>> http://bin.cakephp.org/view/209161709
>>
>> The command on line 7 shows that I got to the desired location, so the
>> path is valid (I suspected that I had fat-fingered the path and hence
>> the error, until I found out it switched correctly).
>>
> Too many closing parens on the first line.  Perhaps the error message
> could add something along  the lines of "extra closing parenthesis?" 
> That would make it clearer.

You can do that in your ~/.clisprc :

[5]> (set-macro-character #\)
          (lambda (stream ch) 
            (declare (ignore stream ch))
            (error "extra closing parenthesis")))

T
[6]> (+ 1 2))
3
[7]> 
*** - extra closing parenthesis
The following restarts are available:
ABORT          :R1      Abort main loop
Break 1 [8]> :q
[9]> 


Or you can even make it just a warning, ignoring superfluous closing parentheses:

[9]> (set-macro-character #\)
          (lambda (stream ch) 
            (declare (ignore stream ch))
            (warn "extra closing parenthesis")
            (values)))
T

[13]> (+ 1 2)) (* 3 4)))
3
[14]> 
WARNING: extra closing parenthesis
12
[15]> 
WARNING: extra closing parenthesis
WARNING: extra closing parenthesis

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: What happened when I changed directories?

[Raymond T. <toy...@gm...>]

On 5/31/12 6:14 PM, Yves S. Garret wrote:
> Hi guys.  I changed directories in clisp with (ext:cd "path/to/file")
> and got this... could some please explain why I got this error and how
> could I avoid it?
>
> http://bin.cakephp.org/view/209161709
>
> The command on line 7 shows that I got to the desired location, so the
> path is valid (I suspected that I had fat-fingered the path and hence
> the error, until I found out it switched correctly).
>
Too many closing parens on the first line.  Perhaps the error message
could add something along  the lines of "extra closing parenthesis?" 
That would make it clearer.

Ray

What happened when I changed directories?

[Yves S. G. <you...@gm...>]

Hi guys.  I changed directories in clisp with (ext:cd "path/to/file") and
got this... could some please explain why I got this error and how could I
avoid it?

http://bin.cakephp.org/view/209161709

The command on line 7 shows that I got to the desired location, so the path
is valid (I suspected that I had fat-fingered the path and hence the error,
until I found out it switched correctly).

[ clisp-Bugs-3530379 ] configure --with-threads hangs on Mac OS

[SourceForge.net <no...@so...>]

Bugs item #3530379, was opened at 2012-05-28 17:49
Message generated for change (Comment added) made by janssen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: multithreading
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Janssen (janssen)
Assigned to: Vladimir Tzankov (vtz)
Summary: configure --with-threads hangs on Mac OS

Initial Comment:
When I try to build clisp-2.49 with --with-threads=POSIX_THREADS, the build hangs, on both OS X 10.5 and 10.6.  The issue seems to be some of the clisp.m4 macros that run clisp into a pipe, e.g.

/tmp/clisp-2.49/src/clisp -K boot  -E UTF-8 -Epathname 1:1 -Emisc 1:1 | head -n 1

This works fine if building without threads, but hangs (hard) when threading is specified.

----------------------------------------------------------------------

>Comment By: Bill Janssen (janssen)
Date: 2012-05-29 18:45

Message:
I'm on 10.5, but I checked out the source tree, and tried it.    That
unfortunately fails thusly:

gcc-4.2 -I/local/PARC-QM/include -I/tmp/clisp/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit
-Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations
-falign-functions=4 -pthread -DUNIX_BINARY_DISTRIB -DENABLE_UNICODE
-DMULTITHREAD -DPOSIX_THREADS -DDYNAMIC_FFI -DDYNAMIC_MODULES -DNO_READLINE
-DNO_GETTEXT -L/local/PARC-QM/lib  ../utils/comment5.c -o comment5
In file included from /usr/include/sys/time.h:198,
                 from /tmp/clisp/src/gllib/sys/time.h:39,
                 from /tmp/clisp/src/gllib/sys/select.h:59,
                 from /usr/include/unistd.h:515,
                 from /tmp/clisp/src/gllib/unistd.h:44,
                 from /tmp/clisp/src/gllib/stdlib.h:90,
                 from ../utils/comment5.c:29:
/tmp/clisp/src/gllib/time.h:469: error: expected ‘;’, ‘,’ or
‘)’ before ‘__timer’
/tmp/clisp/src/gllib/time.h:491: error: expected ‘;’, ‘,’ or
‘)’ before ‘__timer’
make: *** [comment5] Error 1
holmes : /tmp/clisp/src 227 % 

----------------------------------------------------------------------

Comment By: Vladimir Tzankov (vtz)
Date: 2012-05-28 23:35

Message:
Can you check out the source tree and try it? This is supposed to be fixed
there and works for me on 10.6 and 10.7.

----------------------------------------------------------------------

Comment By: Vladimir Tzankov (vtz)
Date: 2012-05-28 23:35

Message:
this is the standard request for more information.
1. what is your platform? 
   ("uname -a" on a Unix system)
   compiler version?  libc (on Linux)?
2. where did you get the sources?  when? 
   (absolute dates are prefered over the relative ones)
3. how did you build CLISP? (what command, options &c)
   please do a clean build (remove your build directory and
   build CLISP with "./configure --build build" or at least
   do a "make distclean" before "make")
4. if you are using pre-built binaries, the problem is likely
   to be in the incompatibilities between the platform on which
   the binary was built and yours;
   please try compiling the sources.
5. what is the output of (lisp-implementation-version)?
6. what is the value of *features*?
7. please supply the full output (copy and paste) 
   of all the error messages.
If you cannot build CLISP, you can obviously skip 5 and 6, 
but then you should provide more information in 1.
please see <http://clisp.cons.org/clisp.html#bugs> 
for more information.
Thanks.

PS. This bug report is now marked "pending" 
    and will auto-close unless you respond
    (in which case it will auto-re-open).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355

[ clisp-Bugs-3530379 ] configure --with-threads hangs on Mac OS

[SourceForge.net <no...@so...>]

Bugs item #3530379, was opened at 2012-05-28 17:49
Message generated for change (Comment added) made by vtz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: multithreading
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Janssen (janssen)
Assigned to: Vladimir Tzankov (vtz)
Summary: configure --with-threads hangs on Mac OS

Initial Comment:
When I try to build clisp-2.49 with --with-threads=POSIX_THREADS, the build hangs, on both OS X 10.5 and 10.6.  The issue seems to be some of the clisp.m4 macros that run clisp into a pipe, e.g.

/tmp/clisp-2.49/src/clisp -K boot  -E UTF-8 -Epathname 1:1 -Emisc 1:1 | head -n 1

This works fine if building without threads, but hangs (hard) when threading is specified.

----------------------------------------------------------------------

>Comment By: Vladimir Tzankov (vtz)
Date: 2012-05-28 23:35

Message:
Can you check out the source tree and try it? This is supposed to be fixed
there and works for me on 10.6 and 10.7.

----------------------------------------------------------------------

Comment By: Vladimir Tzankov (vtz)
Date: 2012-05-28 23:35

Message:
this is the standard request for more information.
1. what is your platform? 
   ("uname -a" on a Unix system)
   compiler version?  libc (on Linux)?
2. where did you get the sources?  when? 
   (absolute dates are prefered over the relative ones)
3. how did you build CLISP? (what command, options &c)
   please do a clean build (remove your build directory and
   build CLISP with "./configure --build build" or at least
   do a "make distclean" before "make")
4. if you are using pre-built binaries, the problem is likely
   to be in the incompatibilities between the platform on which
   the binary was built and yours;
   please try compiling the sources.
5. what is the output of (lisp-implementation-version)?
6. what is the value of *features*?
7. please supply the full output (copy and paste) 
   of all the error messages.
If you cannot build CLISP, you can obviously skip 5 and 6, 
but then you should provide more information in 1.
please see <http://clisp.cons.org/clisp.html#bugs> 
for more information.
Thanks.

PS. This bug report is now marked "pending" 
    and will auto-close unless you respond
    (in which case it will auto-re-open).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355

[ clisp-Bugs-3530379 ] configure --with-threads hangs on Mac OS

[SourceForge.net <no...@so...>]

Bugs item #3530379, was opened at 2012-05-28 17:49
Message generated for change (Tracker Item Submitted) made by janssen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: multithreading
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Janssen (janssen)
Assigned to: Vladimir Tzankov (vtz)
Summary: configure --with-threads hangs on Mac OS

Initial Comment:
When I try to build clisp-2.49 with --with-threads=POSIX_THREADS, the build hangs, on both OS X 10.5 and 10.6.  The issue seems to be some of the clisp.m4 macros that run clisp into a pipe, e.g.

/tmp/clisp-2.49/src/clisp -K boot  -E UTF-8 -Epathname 1:1 -Emisc 1:1 | head -n 1

This works fine if building without threads, but hangs (hard) when threading is specified.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3530379&group_id=1355