Re: CLISP EMACS SWANK remote connection crash

On Thu, 3 Oct 2019 at 09:40, C Habs <[email protected]> wrote:

>
>
> On Thu, 3 Oct 2019 at 00:01, Vladimir Sedach <[email protected]> wrote:
>
>>
>> C Habs <[email protected]> writes:
>>
>> > I was hoping that someone on here was using  EMACS, SLIME and CLISP as
>> an
>> > environment and it was all working fine at the 'slime-repl   (32bit of
>> > course for now). Then I might ask to see the .emacs and .clisprc.lisp
>> > files  and any other pertinent config.  I presume no one uses that
>> setup,
>> > or if they are its either a) they have no problem b) they are 64bit so
>> dont
>> > see it necessarily or c) a.n. other.
>>
>> From everything you describe, it looks like CLISP on 32-bit x86 is
>> the culprit here. I have a couple of 32-bit x86 OpenBSD machines, I
>> will see if I can build CLISP and reproduce the issue there.
>>
>> --
>> Vladimir Sedach
>> Software engineering services in Los Angeles https://oneofus.la
>
>
> That's very helpful and kind of you - thank you.
> Habs
>


Inbetween time, @Richard Cranium on linuxquestions forums ran a few tests
(32bit virtual machine, clisp/slime/emacs etc) and ended up with the
following:

*** - handle_fault error 2 ! address = 0x408 not in [0x206ec004,0x20924874) !
SIGSEGV cannot be cured.  Fault address = 0x408
GC count: 342
Space collected by GC: 0 208030496
Run time: 4 275000
Real time: 18 610303
GC time: 1 14800
Permanently allocated: 94080 bytes.
Currently in use: 4375336 bytes.
Free space: 20 bytes.


It does seem particularly related to 32bit - it does seem to be CLISP
related ?

Regards
Habs

_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list