Hi Greg, thanks for the detailed analysis. My guess is it doesn't depend on the engine but it is triggered when the analyzed move is added to the current (probably complex) game. It is pretty easy to debug SCID on Linux, something like: sudo apt-get install build-essential gdb cmake tcl-dev git clone https://git.code.sf.net/p/scid/code scid-code cd scid-code mkdir Debug && cd Debug cmake .. -DCMAKE_BUILD_TYPE=Debug && make gdb scid
That will give you the exact line where the buffer overflow happened and will be of great help. Bye, Fulvio > Il 24/07/2020 02:39 Greg Marks <gtma...@gmail.com> ha scritto: > > > I've discovered what seems to be a workaround for the buffer overflow > problem I described in my June 23, 2020, message to this list. > This might hint at the source of the problem (or it might mean that > the problem is now moot). > _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
