Re: Bug in (env)?
Alexander Burger writes: Hi Alex, >> hmm... I just downloaded the new (??) version and it still crashes when >> I type (env) directly after start-up ... > > Sorry, the fix was not complete. :( > > > Though it worked for me yesterday, > >$ bin/picolisp >: (env) >-> NIL > Now it works for me too: ,-- | $ ./pil + | : (env) | -> NIL `-- -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Bug in (env)?
Hi Thorsten, > hmm... I just downloaded the new (??) version and it still crashes when > I type (env) directly after start-up ... Sorry, the fix was not complete. :( Though it worked for me yesterday, $ bin/picolisp : (env) -> NIL I noticed that it did _not_ work in a debug break: $ ./pil + : (!) NIL ! (env) Segmentation fault (core dumped) The handling of the frame pointer was still wrong. Now it should be all right. Thanks again! - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Bug in (env)?
Alexander Burger writes: Hi Alex, > I fixed it, and uploaded a new testing version. hmm... I just downloaded the new (??) version and it still crashes when I type (env) directly after start-up ... -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Bug in (env)?
Hi Thorsten, > in the newest testing version on 64bit Archlinux PicoLisp terminates > when I call (env) without args. A bug? Yes, indeed! 'env' crashed when called at the top level (i.e. without any existing bindings). Same for 'trail' and 'up'. The bug was introduced recently by a check for debug break. I fixed it, and uploaded a new testing version. Many thanks for the hint! ♪♫ - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Bug in (env)?
Hi Alex, in the newest testing version on 64bit Archlinux PicoLisp terminates when I call (env) without args. A bug? ,--- | : (env) | Speicherzugriffsfehler | $ `--- -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
