I have just remembered this problem, reported last August. I found, after
installing Fedora32 on a new PC acuired to replace my ancient desktop PC, that
there was an obscure problem in Ved. I kept finding that if I edited a file for
a long time ved would crash with this message, leaving me with a pop11 prompt:
<<<<<<< Access Violation: PC = 00007FFFF7B12890, Addr = 00000007FF6200F0, Code
= 1 >>>>>>>
;;; MISHAP - serr: MEMORY ACCESS VIOLATION (see above)
;;; PRINT DOING
;;; DOING : do_autosave_backup check_and_save_file check_autosave rawcharin
runproc
;;; editing: /home/axs/mail/xxxstuff.txt, ON LINE 1
Pop11 was still running after that, so I could type 'ved' and continue with my
edit. The crash was then not repeated: so something happened only the first time
autosave ran.
I then tried using the old 32-bit Poplog and found that it did not have this
problem.
My workaround for 64-bit poplog was to disable autosaving, on the basis of the
contents of this file:
$usepop/pop/lib/ved/ved_autosave.p
I can't recall which kernel I was using when I reported that problem but I have
just confirmed that (if I allow autosaving) it is present in kernel
5.6.6-300.fc32.x86_64 which I am now using because it allows me to run poplog,
which I can't do in the more recent kernels from 5.8 onwards.
I mention this now because it occurred to me that this problem may come back to
life again if current attempts to make poplog work in 5.8 kernels succeed.
There remains a puzzle as to why this problem did not affect the older 32 bit
poplog, version 15.65, still available here:
http://www.cs.bham.ac.uk/research/projects/poplog/bham-linux-poplog-prelinked-v15.65-180514.tar.gz
With instructions here:
http://www.cs.bham.ac.uk/research/projects/poplog/latest_poplog/latest-poplog.html
That 32-bit version of poplog still works without any problems on my 5.6.6
kernel machine, but
stopped working from 5.8 when 64-bit poplog stopped working.
Aaron
http://www.cs.bham.ac.uk/~axs
