functions when an excpetion is pending.

Some work still needs to be done on js_msgbase.c,  js_user.c, and mailsrvr.c

Only js_ValueToStringBytes() still leaks.

      on the floor of Deuce's computer room
Cyan: Rob's on his way
* Deuce throws his coffee on it.

Last commit before stuff starts to break.

js.gc_counter, js.gc_last_bytes, js.bytes, and js.max_bytes
Since these properties rely on internal JS context structure offsets, they're
not always compatible with replaced (upgraded or downgraded) JS library
(shared object or DLL) and can cause crashes in some cases. They can be
useful in some debugging cases, so I'm leaving them in the debug build, but
use with caution.

value of js.auto_terminate (e.g. the irc.js could not restore the original
value, thus re-enabling auto-terminate upon exit of the IRC client).

but run with a different version of libjs.so.

(potentially) non-blank for external JS modules configured in SCFG->External
Programs, as well as those executed from jsexec. If the startup_dir is
specified in SCFG and no path is given for the .js file, it will look in the
startup_dir first. js.startup_dir will be an empty string for all other cases
(currently).

than dynamically allocated string list. Also, allow a blank JavaScriptLoadPath
to be specified in the sysop's sbbs.ini if they wish. This resolves the memory
leak issue with this startup parameter.

created:
js.exec_path - full path and filename of file executed
js.exec_dir - directory of executed file
js.exec_file - filename executed (with no path)

Configurable via ctrl/sbbs.ini file JavaScriptLoadPath key value
(comma-separate listed of search directories), default value is "load".
This list is exposed in the JS object model via the js.load_path_list array
(may be modified by scripts).
For JSexec, the default load path list may be over-ridden with the '-i' option.
For relative load paths (e.g. not beginning with '/' or '\'), the path is
assumed to be a sub-directory of the (configurable) mods or exec directories
and is searched accordingly.
So, by default, load("somefile.js") will search in this order:
mods/load/somefile.js
exec/load/somefile.js
mods/somefile.js
exec/somefile.js

loop because the termination (e.g. dropped TCP session) flag is set:
Disable the auto-termination when evaluting on-exit strings.

bugs.

under certain circumstances.

Enabling shared runtimes passes the initial touch testing.

This may have Win32 issues with DLLs.

max_bytes) crash when accessed, so removing for now.