Re: [E-devel] Efreet bug when desktop files change

[Carsten H. (T. R. <ra...@ra...>]

On Fri, 1 Apr 2011 15:45:20 +0200 Leif Middelschulte
<lei...@gm...> said:

> 2011/4/1 Carsten Haitzler <ra...@ra...>:
> > On Fri, 1 Apr 2011 09:16:39 +0200 sd...@ta... said:
> >
> >> I don't get it. Isn't eet supposed to detect corrupt files? I guess it is
> >> something inside efreet, tried to find it but didn't see anything weird.
> >
> > well only as corrupt as eet will fail finding stuff in the header. rememebr
> > eet files generally are:
> >
> > [header]
> > [key hash/list + data offset per key]
> > [data1]
> > [data2]
> > [data3]
> > ...
> >
> > so it could happily write half of data3 - but then loading data3 key at ALL
> > will fail. shared string dict also complicates that a bit as string dict is
> > mmaped.
> >
> No 'verified data end'-tag?

no. but file size will not be right. you'll be only reading some of data3
before it'll stop. unless of course it writes extra INVALID data - that;'d be a
filesystem bug. it's data that no app ever write/provided unless it explicitly
wanted corrupt data in an eet file.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ra...@ra...