dumaiu/cl-cudd

Common lisp bindings to CUDD. Fork of a fork of a fork of Neronus's original SWIG-based wrapper.

cl-cudd's Issues

HACK: Location of `libcudd` hard-coded

In 1-0-0-library.lisp, I set the path to /usr/local/lib/libcudd.

• TODO: check cffi:*foreign-library-directories*.

GC finalization can corrupt the CUDD unique tables

Placing calls to (cudd-check-keys) and (cudd-debug-check) inside the finalizer callbacks will produce abundant error messages. Keep one eye on *error-output* and the other on uiop:*stderr*.

• Perhaps related to issue 2 here?

  • Not likely... Finalizers themselves should eliminate that and its (with-pointers) countermeasure.

• Do I need to lock CUDD when creating a variable?

Impossible to kill/reload the CUDD manager without CFFI memory errors

The only way to "clean" the CUDD manager is to call (cudd-quit) and spawn a new one. To do this safely, not to mention thread-safely, requires a lot of cleanup; the Lisp node handles need to have all their pointers zeroed.

• The macro to be tested: (manager-reinitf).
• See branch WIP/manager-reinitf.
• TODO: How should we treat CUDD nodes which are semipermanent? The ones representing T, F, and variables?

Rebase `WIP/debug-finalizer/dev` branch