Subject: [clisp-list] Number of c functions in a external module

From: "Hoehle, Joerg-Cyril" <[email-masked]>
Date: Tue May 21 02:26:02 2002

Dan Stanger wrote:
> Is there some sort of hard limit (around 370 or so) functions in a c module?
No.

>lisp.run is getting a signal 11, access violation when it tries to dump
>lispinit.mem after it loads my module.
Uh oh, sounds like some internal structure is corrupt.
And you can do as much Lisp as you want prior to SAVEMEM? E.g. multiple (ext:gc), load large files, etc.

>The access violation occurs in package.d, when I add 1 more
>function, and disappears when I comment it out.
And if you add another one function?

>Does this sound familiar to anyone?
No.

BTW, which version of CLISP are you using? My init_modules patch (past 2.28) fixed some issues w.r.t. module_initialization and some potential uninitialized pathname or encoding variables. Uninitialized variable -> later GC crash, or possibly post GC crash (via old pointers to moved objects).

Not much help here,
	Jorg Hohle.