#294 .asd files getting damaged by CLISP 2.36

clisp (525)

Version used: CLISP 2.36 on Windows
CLISP 2.35 doesn't produce a bug in the same circumstances.

A bug occured while loading UnCommonWeb framework with
ASDF. Three .asd files were irreparably damaged after
(unsuccessful) compilation. They were replaced by emty
0-byte files. The files in question are arnesi.asd,
yaclml.asd and rfc2388.asd. Other involved .asd files
were untouched. The fact that version 2.35 doesn't
demonstrate such destructive behavior leads me to
believe that the bug was introduced with CLISP 2.36.


  • Sam Steingold

    Sam Steingold - 2005-12-15

    Logged In: YES

    since I use neither UnCommonWeb nor ASDF,
    you will need to provide a self-contained test case
    so that I will be able to debug this.
    I will mark this pending -
    it will re-open when you provide the additonal information.

  • Sam Steingold

    Sam Steingold - 2005-12-15
    • status: open --> pending
  • Timofei Shatrov

    Timofei Shatrov - 2005-12-15
    • status: pending --> open
  • Timofei Shatrov

    Timofei Shatrov - 2005-12-15

    Logged In: YES

    Update: I was able to reproduce this bug with CLISP 2.35 but
    it seems to only happen when CLISP is started from a desktop
    icon. It's a very strange bug. I'll see what I can do with
    test case...

  • Timofei Shatrov

    Timofei Shatrov - 2005-12-15
    • status: open --> pending
  • Sam Steingold

    Sam Steingold - 2005-12-27
    • status: pending --> pending-invalid
  • SourceForge Robot

    • status: pending-invalid --> closed-invalid
  • SourceForge Robot

    Logged In: YES

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks