#122 Xmaxima and `could not find`...


$ xmaxima

load("init.mac") ## or whatever file which is not
## in the path variable

The only answer is:

Could not find

and the system gets hung there. It should print the

"Could not find `init.mac' using paths in

(combined values: [/home/xpfa/.maxima/###.{mac,mc},
/usr ...."



Maxima version: 5.9.0rc1
Maxima build date: 8:38 9/9/2002
host type: i686-pc-linux-gnu
lisp-implementation-type: CLISP
lisp-implementation-version: 2.29 (released 2002-07-25)
(built 3236605690) (memory 3240545944)



  • Mike Clarkson

    Mike Clarkson - 2002-09-18

    Logged In: YES

    This is serious, and I think should be fixed before 5.9.0 goes final.

    Is it the lisp closing itself on errors?


  • Mike Clarkson

    Mike Clarkson - 2002-09-18
    • priority: 5 --> 8
  • Mike Clarkson

    Mike Clarkson - 2002-09-18
    • milestone: --> Fix_for_5.9.0
  • James Amundson

    James Amundson - 2002-09-18

    Logged In: YES

    I can add some more information. The bug only occurs with
    clisp and xmaxima on my system. cmucl and gcl are OK. All
    three lisps are OK with plain maxima.

    I've also noticed that sometimes more of the error message
    shows than others. It seems to be related to how much output
    precedes it. For example

    (C1) load("xxx");


    Could not find `xxx' using paths in

    (combined values: [/home/amundson/.maxima/###.{mac,mc},

    (C1) ratexpand((x+y+z)^20);
    <output supressed>
    (C2) load("xxx");

    only gives


    My guess is that the problem is in the socket code.


  • Mike Clarkson

    Mike Clarkson - 2002-09-18

    Logged In: YES

    There are two issues here - maxima dying on a trivial error, and xmaxima not getting
    the complete error message.

    The second part doesn't worry me yet - if maxima is dying, it's unpredictable how much
    xmaxima will get back from a socket connected to the dying maxima.

    But the first part should get fixed, because maxima should not be dying on
    a trivial error. I assume it;s something to do with the load command itself,
    because maxima isn't usually dying on simple errors. Maybe a catch down
    in lisp will help (I'm just guessing - I haven't looked at the lisp code).

    It would be nice to convince ourselves that the load command is the only one that
    does this. The error reported in the mailing list on loading a non-existent plot.o
    is of course the same error. I have fixed the xmaxima code now so that you get
    a detailed error message when the local xmaxima dies, so at least we can see this.

    Unfortunately I can confirm that load("foo.max") kills the latest rc1 gcl under Windows.
    However, I seen always to get the complete error message.


  • Robert Dodier

    Robert Dodier - 2005-08-22
    • status: open --> pending
  • Robert Dodier

    Robert Dodier - 2005-08-22

    Logged In: YES

    I can't reproduce this bug (running Maxima 5.9.1cvs built
    2005/03/31 on clisp 2.31 and 5.9.1cvs built 2005/08/21 on
    clisp 2.33, redhat fedora 1.3). Seems likely that it's been
    fixed, maybe someone else can retest.

  • SourceForge Robot

    • status: pending --> closed
  • 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