Review Request: Ask the user whether to clean DUChain repository after multiple crashes.

[David Nolden]

In rare cases, also a technically valid repository can make kdevelop crash,
because it simply preserves the state. There must be a way to reset the
state in case of problems, which the automatic deletion does.

Am 09.03.2011 09:04 schrieb "Esben Mose Hansen" <kde at mosehansen.dk>:

On Tuesday 08 March 2011 23:52:13 Dmitry Risenberg wrote:
> The bigger question - is this code still...
Wouldn't the right way to do that be to introduce some checksums so
that we can actually test if the repository is corrupt? Say, when
updating the repository, it could

1.a. update the repository
1.b at this stage, the repository is uncorrupt.
2. update the checksum

That way, if we unhappily crashed during 1.a, some checksum would
fail and tip KDevelop off.

Of course, that will not work if the cause is that some code is simply
writing nonsense to the repository.

--
kind regards, Esben

--
KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110309/36970c2f/attachment.html>