> -----Original Message----- > From: Michael Petch [mailto:[email protected]] > Sent: 29 May 2013 22:49 > To: [email protected]; Ian Shaw > Subject: Re: [Bug-gnubg] Crash running a commad file - Fix & Workaround > > On 29/05/2013 12:49 PM, Michael Petch wrote: > > I can't reproduce this situation exactly but I did discover an anomaly > > (possibly related) that causes a crash when the file name has spaces > > in it and one uses the load command without quotes > > > > What happens if you change the command to: > > > > load commands "c:\users\ian\saved games\43Z-reply.txt" > > > > Note that there are double quotes around the string. > > > > Can you send me a copy of your gnubgautorc file (probably in > > c:\Users\ian\.gnubg ) . > > I believe I found the problem and it only affects Win32 builds. If the > filename > parameter in the "load commands" command doesn't use quotes, there is a > potential crash after the commands are executed. I have committed a fix for > this issue into CVS. > > Can you verify that if you put quotes around the filename that the issue > disappears? If that works it could be a temporary work around until the next > Windows release. >
Bingo! Double quotes around the string succeeds. I really should have thought of that. Cheers, Ian _______________________________________________ Bug-gnubg mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-gnubg
