Re: [Bug-gnubg] import mat bug

[Jim Segrave]

On Tue 02 Sep 2003 (00:10 +0200), address@hidden wrote:
> Version: 1.1324 030831  on Windows XP
> 
> If I  import a corrupt  .mat file gnubg  crashes (both GUI  and no-gui).
> This  may  seems  trivial  but  I'm running  batch  scripts  to  process
> thousands of .mat files which occasionally are corrupt and would like to
> recover gracefully from it.
> 
> > import mat bug.mat
> 
> outputs:
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Assertion failed: *pc <= 4, file import.c, line 458
> This application has requested the Runtime to terminate it in an unusual
> way.
> Please contact the application's support team for more information.
> Unrecognised move "Pos=-b----E-C-A-eE---c-e----A-/0" in .mat file.
> WARNING: Invalid move: " 25/23 13/8" encountered
> WARNING: Invalid move: " 13/7 8/7" encountered
> WARNING: Invalid move: " 25/21 7/5" encountered
> WARNING: Invalid move: " 25/20 21/16 21/16 20/15" encountered
> WARNING: Invalid move: " 16/12 15/12" encountered
> WARNING: Invalid move: " 12/6 6/4" encountered
> WARNING: Invalid move: " 6/1 6/4" encountered
> WARNING: Invalid move: " 1/0 1/0" encountered
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I think the asserts (which cause gnubg to exit) were put in because
the snowie.mat file is undocumented and has been reverse
engineered. Getting a crash is the only way to get people to supply
.mat files which exhibit as yet not-understood features. 

Can you email me the .mat files which fail? I can look at adding
support for what's missing when I see the failure modes.

-- 
Jim Segrave           address@hidden