X-FREEZE Hard error occurred

We have an error message that we do not know how to handle. The message
below shows up after picking the toolbar icon button, which loads a lisp
function (if not loaded) then runs it. However, it will not run because of
this message:

Command: X-FREEZE Hard error occurred *** internal stack limit reached
(simulated)

Can you give us an idea of why this is happening? Originally, the icon is
set up to run this:

^C^C(if (not C:XREFUNLK) (load (strcat drv0 "XREFUNLK")));XREFUNLK;

I wanted to simplify this and put the loading part of the code into our main
lisp file, ACAD.lsp, and have the toolbar icon button to just show this:

^C^CXREFUNLK;

That way, we don't have to use the toolbar icon to run the command. We
would be able to run it from the command line (or in our "Launch Pad" macro
unit).

Has anyone got a solution?
Thanx
David

 

David,

Load the function via the menu's .mnl file, and then you can discard that
lisp statement.

--
R. Robert Bell


We have an error message that we do not know how to handle. The message
below shows up after picking the toolbar icon button, which loads a lisp
function (if not loaded) then runs it. However, it will not run because of
this message:

Command: X-FREEZE Hard error occurred *** internal stack limit reached
(simulated)

Can you give us an idea of why this is happening? Originally, the icon is
set up to run this:

^C^C(if (not C:XREFUNLK) (load (strcat drv0 "XREFUNLK")));XREFUNLK;

I wanted to simplify this and put the loading part of the code into our main
lisp file, ACAD.lsp, and have the toolbar icon button to just show this:

^C^CXREFUNLK;

That way, we don't have to use the toolbar icon to run the command. We
would be able to run it from the command line (or in our "Launch Pad" macro
unit).

Has anyone got a solution?
Thanx
David

 

That was an old Rel 14 habit, eh?

 

Not really. It still makes sense if the function is rarely used. However,
you can *still* place an autoloading statement in the .mnl file, rather than
in the .mns itself. That being said, your "autoloading" statement as written
won't work as you think with the .mnl. The C:XREFUNLK will be unbound (nil)
at that point, so will load it anyway. If you want a true autoload, look at
the (autoload) function that Autodesk already provides.

Mind you, that still doesn't address the endless loop you have going on. The
only clue I can offer is that the crash appears in the function X-Freeze,
and is probably looping on loading itself or C:XREFUNLK.