Nikodemus Siivola writes:
> Vadim V. Zhytnikov wrote:
>> I maintain sbcl for one of Linux distros (ALT Linux)
>> and one of our users report the following problem with
>> sbcl 1.0.5. He uses sbcl with Maxima on his notebook.
>> And when system is restored from HDD hibernation
>> sbcl+Maxima session can't be restored.
>> Whenever he tries to enter a new command he get
>> the following error:
>> Maxima encountered a Lisp error:
>> Error during processing of --eval option "(cl-user::run)":
>> The value -23972638 is not of type UNSIGNED-BYTE.
>> Automatically continuing.
>> To reenable the Lisp debugger set *debugger-hook* to nil.
>> The important point is what with earlier sbcl version,
>> namely 1.0.2, everything just works fine and no such
>> problem is observed.
> Is the Maxima version with 1.0.2 same?
> Does the length of the hibernation matter?
> What happens if he sets *debugger-hook* to NIL before
> hibernation? (Hopefully he'll get a backtrace that will
> enlighten us.)
We start investigating problem in depth and
discovered the source of troubles. It is
neither sbcl (any version) nor Maxima but
some undeleted remnants of old builds.
I'm sorry for disturbance!
With best regards,
Vadim V. Zhytnikov