[bt-devel] Bookshelf manager bugs

[Eeli Kaikkonen]

Eeli Kaikkonen wrote:

> 
> There have been crashes with the bookshelf manager. As a quick fix I 
> could disable concurrent installing. It would work just like before but 
> only one module installation would be active at the same time. Now it 
> can have three concurrent installations from one source.
> 
> Technical notes:
> I can't say for sure that the problem is not in the code written by me, 
> but I think it's in the Sword library or possibly in the ftp library 
> used by the Sword library. Most probably it's the Sword library. It 
> means that if we want to have concurrent installing we have to replace 
> the Sword install manager. It would be much work and means duplicating 
> the code, copying it from the Sword library to our own codebase. The 
> case would be easier if the problem is in the ftp library because we 
> could just use the QFtp class instead and in return would get finer 
> control over the connection and failure situations.
> 
> Ok, I will disable concurrent installing. Please people, test it again 
> and report if it work or not. If it still crashes the bug is much easier 
> to find when I know it's my own code. And btw, start BibleTime with 
> --debug switch and if you find a crash (anywhere), please attach the 
> debug output and possibly the trace log from KDE crash handler.

I haven't disabled concurrency yet but I did some more testing with the 
manager. I have written in wiki about another bug: it ends up eating 
processor time (starvation or deadlock). By adding debug statements I 
found out that it happens when it calls 
sword::InstallMgr::installModule(). This very strongly suggests that the 
problem is in sword or in ftp library. Probably I should add debugging 
to sword library and recompile it to get more information.

This didn't happen with my older machine but happens quite often with 
the new dualcore.


Then the crashes... There might be several different bugs. I already 
thought about some possibilities with signals/slots. If that's correct I 
can possibly cure it by changing my own code. If it still crashes I 
presume it's in sword or ftp library. Again, it would help tremendously 
if someone could catch the crashes with backtraces. It's also important 
to know the exact situation: is it in the beginning or when a download 
is ending, does it happen with one/several modules or one/several sources.

ATM I'm too busy to commit any changes.

I'm grateful if someone else can help. In any case these bugs must be 
solved somehow before the final release or RC. I'm OK with the idea of a 
beta having known crashes if it helps people to test and find the 
reason, but then we need testers, not just a release.

--Eeli Kaikkonen