Stephen Westfold <westfold@...> writes:
> This turned out to be a problem with our hack for implementing a
> "setenv" function and nothing fundamental with sbcl. The problem
> occurred when an environment variable was not set and the getenv of it
> returned NIL and then this was later called as an argument to setenv
> which was expecting a string. Most of our scripts and environments set
> this environment variable, so that is why it was only a problem in
> particular cases.
Am I understanding this right: you essentially did
in C, where NIL is the Lisp NIL? Or did you call it via
the alien interface?
The reason I am asking is that while there is nothing to be done about
it if C scribbles over Lisp memory, there should be something to be
done about it if you were able to pass a NIL to an alien function
expecting a string in a way that ended up corrupting memory...
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."