Waldek, Thanks for instructions on debugging following my report about > > > <<<<<<< Access Violation: PC = 00007FFFF7B12890, Addr = 00000007FF6200F0, > > > Code = 1 >>>>>>>
> .... > As I wrote year ago, way to investigate this is to run Poplog inside > gdb: > > gdb pop/pop/ved > > At gdb prompt type > > run > > When ved crashes you should see info about where it crashed. > ... I discovered that before I could run gdb on my machine I had to install a lot of fedora packages (using 'dnf install...'). When prompted I blindly said 'yes' to all of them. However, it looks as if using gdb properly in conjunction with ved will require some learning and more time than I can spare just now, so I am shelving this in order to catch up with other things. I shall however investigate whether the same problem arises on my laptop running Fedora31, on which I have just installed the latest version of poplog, and will set up a test. So far there's no sign of the problem. I suppose it is possible that there's an obscure bug in some recently updated Fedora 32 library. Aaron
