[Gcl-devel] strings copied across heap/local data boundaries

[Mike Thomas]

Hi Camm.

I finally got gdb onto a repeatable Maxima "ignore-errors" session and found
that tracing through the problem code made the problm disappear.
Fortunately the section of code was quite short (file.d open_stream).  I
noticed that there wasa string copy there from a Lisp object into a string
buffer and that triggered an earlier hunch you had which I believe was about
relocation messing up string manipulation.

So I stuck BEGIN/END_NO_INTERRUPT into open_stream and lo and behold the
formerly repeatable error was replaced by another repeatable error of
similar nature much later in the Maxima build - at the point where all the
object modules are being loaded after compilation.  This particular bug has
never manifested at that late stage before so I take this as a positive sign
and an indication that we need to systematically track down similar
unbracketed string/data copies across local/heap boundaries of which there
appear to be several including, significantly, "o/pathname.d".

Late again

Mike Thomas.