> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Michael > Nordstr�m > Sent: Monday, February 10, 2003 5:22 AM > To: [EMAIL PROTECTED] > Subject: Re: Plucker bug or problem on my device? > > > If I do an Update Documents operation, Plucker > > works for a while, then crashes with a fatal > > exception. > > Must be a Visor problem; it works just fine on my > TRGpro. Have you tried to recreate the same problem > for documents in RAM? Have you tried the latest > unstable version?
I think I may have found the problem, but it leads to another question I'll get to in a moment. > There have been many major changes to the code since > the 1.2 release, but I don't remember to have changed > any *bugs* related to the doclist handling. However, No, the last one I reported you were able to fix, and things have behaved flawlessly since. That's why I was reluctant to consider this a bug, and suspected it might be an issue on my device. (And I believe it was, which I'll describe below.) > there is a bug somewhere in that code (nothing that > would cause the device to crash, though) that > sometimes makes the categories getting out-of-sync. I > haven't been able to come up with a good way to > reproduce that problem, though, so it's kind of > difficult to find. Anyway, I'm currently making major > changes to that code to "isolate" the doclist handling > to one file. I don't believe I've seen that one, and I seem to have a track record of getting bitten by document handling code bugs. :) > I don't think we should add support for deleting non- > existing documents, though. It's not only when you > have removed a document externally that you will end > up in a similar state, e.g. if you move a document > from RAM to an external card (or vice versa) you will > be in the exact same situation, but this time the entry > shouldn't be removed from the list. When you use the > "manually update" option it is your responsibility to > update the list whenever you add new documents, remove > documents, move document to/from an external card, etc. That was going to be another question. I considered the case of a document being moved from RAM to card or vice versa. As long as a manual update actually works, I'll do that. But meanwhile, I _think_ I know what the problem was. I popped the card into my USB card reader, ran chkdsk, and examined the files. I found a couple of Plucker documents which were obviously corrupted (there is no way a novel in Plucker format will take up a whopping 3KB of space - zlib compression isn't _that_ good) and removed them. Once I did so, things seem to have cleared up. So the next question is "What does Plucker look at when it's enumerating files during an update operation?" I can see Plucker crashing if it runs into a bad file, but what qualifies as bad? I assume it looks at the header to determine that the file _is_ a Plucker file? If Plucker needs anything, it may be more robust error handling when it runs into a bad file. This sort of problem is highly unlikely for documents in RAM, but unfortunately too likely for FAT formatted expansion cards. > /Mike ______ Dennis _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
