Hard error occurred *** internal stack limit reached (simulated)

[Poorest Chump]

Has anyone ever seen this error?

"Command: Hard error occurred ***
internal stack limit reached (simulated)"

I'm pretty sure what it means. Sounds like I'm going about this routine the wrong way. AutoCad's trying to keep track of too much code, right? Please confirm.

[scwegner]

Has anyone ever seen this error?

"Command: Hard error occurred ***
internal stack limit reached (simulated)"

I'm pretty sure what it means. Sounds like I'm going about this routine the wrong way. AutoCad's trying to keep track of too much code, right? Please confirm.

My guess is that your code has an infinite loop in it somewhere. Of course, without seeing it...

[madcadder]

Not much help here but...
After hitting google for "autocad" and "hard error" it returned this lisp.
Maybe it will give a direction.

here's the google link
http://www.google.com/search?hl=en&q...2hard+error%22

[madcadder]

also found this bit from one of the links:

;;; Maximal number of arguments to functions like AND
;;; AutoLISP: => (*error* "too many arguments")
;;; VL: no *error* is called, hard error

[scwegner]

Not much help here but...
After hitting google for "autocad" and "hard error" it returned this lisp.
Maybe it will give a direction.

here's the google link
http://www.google.com/search?hl=en&q...2hard+error%22

Exactly what I was saying. If a loop in LISP is infinite or too long, it will cause an error. The MAXSTACK lisp was written to test just how many repetitions AutoCAD could handle.

[stig.madsen]

Sounds like I'm going about this routine the wrong way. AutoCad's trying to keep track of too much code, right?

Too much code, no. Too much code in the stack, yes. Regular loops don't add significantly to the stack unless they're specifically designed to do so (such as creating structures on the fly). Not even infinite loops. As the links suggest, you should only be looking for recursive calls in your code. My guess is that you have a recursive call that lacks an exit condition.

[sloveless]

I've got the same problem except my lisp routine works great in Acad2007, freaks in Acad2008. Any help would be greatly appreciated!

- Scott

[BlackBox]

This is an old thread, but I am now experiencing the stack overflow error. I tested the maxstack routine above and show "No Stack Overflow Occurred" as a result. Also worthy of note, I have 0 selection sets in my current drawing.

(vla-get-count (vla-get-selectionsets *activeDoc*))
;; Count = 0

The routine in question is a simple Copy Rotate routine, loaded from the enterprise server. So far, it's the only command that throws this error. Interestingly, if I drag the .LSP into the drawing, the routine runs fine.

Not sure what's causing this issue, but would really appreciate some help!

[RobertB]

This is an old thread, but I am now experiencing the stack overflow error. I tested the maxstack routine above and show "No Stack Overflow Occurred" as a result. Also worthy of note, I have 0 selection sets in my current drawing.

(vla-get-count (vla-get-selectionsets *activeDoc*))
;; Count = 0

The routine in question is a simple Copy Rotate routine, loaded from the enterprise server. So far, it's the only command that throws this error. Interestingly, if I drag the .LSP into the drawing, the routine runs fine.

Not sure what's causing this issue, but would really appreciate some help!

An autoloader loop?

[BlackBox]

An autoloader loop?

Fixed it.

In this case, it was a toolbar macro converted to a defun incorrectly.

(defun c:CommandName () 
  (if (not (c:CommandName)) ; <- Same name as defun
    (progn
      (load "CommandName")
      (c:CommandName))
    (c:CommandName)) ; <- Loop
  (princ))

The load statement alone should be added to ACADDOC.lsp.

Thanks!