On Mon, 24 Nov 2008, Matt Ackeret wrote: > On Sat, 22 Nov 2008, Patrick Vervoorn wrote: >> I'm still here, even using trn, though it is getting more and more >> unstable as time goes by. Using 'valgrind' I also notice trn is quite >> sloppy with (de-)allocating it's memory... > > (I don't actually have a newsfeed anymore, and haven't tried out any of > the free newsfeeds..) > > But won't valgrind tell you where the memory was _allocated_ too? > In other words, it provides enough info to fix the problem, right? It barfs out a _LOT_ of info, but the generic crash (or rather, the serious leak) seems to occur in the c-library itself, not in trn. I could probably trace it back, but the output says nothing to me, I'm afraid. For me, valgrind is just a wrapper around trn, to keep it running when I encounter a particular nasty set of overviews... Regards, Patrick. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
