Re: exmh_addrs address database truncated

[email protected] wrote:

>For a given input file, the output (ie., after loading the database into exmh
>and then saving to the exmh_addrs file) is consistent. However, the output file
>size varies depending on the order of the input file, and the output file
>doesn't end on the same entry each time.

Perhaps the last good entry is different each time but what about the
next entry in the file for that sort order? Or the next few entries
(depending on buffering)? Perhaps there is something common there.

My guess is that there is some character in your file that the parser
doesn't like. It might be some special character that isn't used anywhere
else. It might be a character with the high bit set (so it looks normal
when displayed). Or it may well be a character that is invisible when
the file is viewed normally (such as a null). You might try od or some
other binary dump.

Since the problem just happened recently, you might concentrate on more
recent additions to the file.
-- 
       Dave Close, Compata, Costa Mesa CA       +1 714 434 7359
       [email protected]              [email protected]
The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We cause accidents.  -- Nathaniel Borenstein