On Fri, 30 Jan 2009, D. Richard Hipp might have said: > > On Jan 30, 2009, at 8:42 AM, Mike Eggleston wrote: > > > This box is fedora core 5 with sqlite3 3.3.3. > > Version 3.3.3 will be three years old tomorrow. From this I'm > guessing you didn't compile SQLite yourself but are using whatever > happen to come with fedora core 5. And there is no telling how they > compiled it..... > > I'd suggest you download the latest sqlite3 command-line shell from > http://www.sqlite.org/download.html > - precompiled and ready to run, and try again using that. > > FWIW, SQLite does not use mmap(), at least not directly. (Maybe the > system malloc() is calling mmap().) So I do not know what is causing > all of those mremap() calls you are seeing in strace. > > D. Richard Hipp > d...@hwaci.com
I had thought of that also, but wanted to wait to see if there is some already known reason this is happening. So, I pulled the source for sqlite-3.6.10.tar.gz, compiled it on the fedora core 5 box, and ran the command again. The data loading is stopping at exactly the same place. Short answer: no change. What's next? Wait. I ran the sqlite3 under script during lunch. I have the same behavior. The script also captured the first line of output from killing sqlite3. The output shows binary characters in an INSERT statement. The bad line is (characters coverted): (oops deleted the line, a few ^P, ^G, and ^0 characters) (found another) INSERT INTO File VALUES (3555,55862,1093685304,1817326624,1799833888,1092633120,'A A Bey BAA Y BGmuHb BFi8Ob BGfR','I A A C^V+I2SKHGKJVuCfW9BcGPWLQ\0\0^C\0g^A ø~^~G§\0^G;^C\0~J\0\0\0ã\r\0\05Ú\0\09P0A 4Rj IGk B A A A'); In vi I finally used :g/[^A-^Z]/d to remove all binary characters. After removing that line I was able to load the entire file without errors. Thanks for the help. Mike _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
