[EMAIL PROTECTED] wrote: > Send Scid-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/scid-users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Scid-users digest..." > > > Today's Topics: > > 1. Re: scid problem with large pgn (Alexander Wagner) > 2. FYI (Alexander Wagner) > 3. Re: scid problem with large pgn (Benoit St-Pierre) > 4. Re: scid problem with large pgn (Mikhail Kalenkov) > 5. Re: scid problem with large pgn (Benoit St-Pierre) > 6. Re: scid problem with large pgn (Marcin Kasperski) > 7. Re: FYI (Richard Vaughn) > 8. Re: FYI (Alexander Wagner) > 9. Re: FYI (Michal Rudolf) > 10. Re: FYI (Alexander Wagner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 29 Jul 2008 07:01:05 +0200 > From: Alexander Wagner <[EMAIL PROTECTED]> > Subject: Re: [Scid-users] scid problem with large pgn > To: Bogdan Burlacu <[EMAIL PROTECTED]> > Cc: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Bogdan Burlacu schrieb: > > Hi! > > >> I am having a bit of a problem with scid... when trying to convert/open >> a 2gb pgn file: >> - when I use pgnscid in a terminal, it starts converting but fails >> at some point, saying "bus error" >> - when I try to open that file in scid, it shows the progress bar >> and then it crashes, probably when it reaches the same point as pgnscid >> > > I think we already had this some time ago and if I remember > correctly the "trick" is to split the PGN to a smaller than > 2G portion. Additionally, I think part of the solution was > that it's not a limit within scid that you hit here but in > other parts of the OS. (Files \approx 2G or larger.) > > Wasn't it a problem of Shivs when he converted CB Mega or > something like that? > > Hello
It is not a file system problem (partition in ext3). I have tried splitting it into 100M files but still no luck, and splitting is also bad because you mess up the pgn. I have even tried compressing the pgn file, getting a 700mb tarball, which still failed with the same error. In my opinion, the problem is with scid on 64bit systems (I run the 64 bit version of gentoo linux). Here's some debugging info: From gdb: (gdb) run /home/master/ChessBase/Database/Work/opening\ encyclopedia.pgn Starting program: /usr/games/bin/pgnscid /home/master/ChessBase/Database/Work/opening\ encyclopedia.pgn Converting file /home/master/ChessBase/Database/Work/opening encyclopedia.pgn to Scid database /home/master/ChessBase/Database/Work/opening encyclopedia: Errors/warnings will be written to /home/master/ChessBase/Database/Work/opening encyclopedia.err. [0% 10 20 30 40 50 60 70 80 90 100] [. Program received signal SIGBUS, Bus error. 0x000000000040f6fa in Position::ReadMove () Current language: auto; currently asm From /var/log/messages: Jul 28 16:53:52 localhost pgnscid[27880] trap stack segment ip:40f6fa sp:7fff7a77f840 error:0 Jul 28 16:56:29 localhost tkscid[16049] trap stack segment ip:435b8a sp:7ffffce583a0 error:0 Jul 28 17:12:58 localhost pgnscid[27992] trap stack segment ip:40f6fa sp:7fffce4bf1b0 error:0 Jul 28 17:15:45 localhost tkscid[27982] trap stack segment ip:435b8a sp:7fff66fa9670 error:0 Jul 28 17:17:00 localhost tkscid[27998] trap stack segment ip:435b8a sp:7fff8deed930 error:0 Jul 28 17:22:17 localhost tkscid[28013] trap stack segment ip:435b8a sp:7ffffb73eff0 error:0 Jul 28 17:25:38 localhost tkscid[28019] trap stack segment ip:435b8a sp:7fffa17a1050 error:0 Notice how it always fails at exactly the same instruction (ip is the same). I did try compiling scid with less optimizations (-Os -march=i686), same results. In the end I gave up and converted that 700M tarball on another (older) computer, which has a intel celeron cpu and a 32-bit gentoo linux, and it worked flawlessly. It seems to me the problem is 64 bit specific, perhaps regarding the kernel stack size. I did look at Position::ReadMove() in position.cpp but did not find anything (yet). ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
