[bt-devel] Bibeltime beta 4 bugs

Martin Gruner bt-devel@crosswire.org
Thu, 23 Jan 2003 19:35:03 +0000


Hey Joachim,

good point about sword. We should start doing some memory debugging. A tool 
you can use is valgrind (http://developer.kde.org/~sewardj/), and there's a 
good kde frontend: kchachegrind (http://kcachegrind.sourceforge.net/), but 
imo ony for cache profiling, not memory debugging.

Martin

Am Donnerstag, 23. Januar 2003 10:14 schrieb Joachim Ansorg:
> I'm curious what the options are :)
>
> on my side it doesn't even open up. At least in the sword cvs thers a mem
> leak which occurs while opening websters. which sword are you using?
>
> Joachim
>
> > On Thursday 23 January 2003 12:13 am, Martin Gruner wrote:
> > > It takes longer than other frontends because only we load the entire
> > > module (the keys, that is) when opening it. However, we use a cache
> > > file for the lexicons, so only the first opening should be slower.
> > > Maybe we should tell the users about that (dialog while cache is
> > > created) so that they don't think BT hangs?
> > >
> > >
> > > mg
> >
> > Well martin like I said I'm running some compile time options that make
> > Webster's open in about 2 seconds the whole interface is running quite
> > fast actually. I very pleased with the results.