Dear Alexey [I'm Cc'in the bugreport and the original submitter of the bugreport to have it recorded in our BTS.]
On Sun, Oct 24, 2010 at 09:14:02AM +0400, Alexey Balakin wrote: > Dear Salvatore > > > Dear Alexey > > > > On Fri, Oct 22, 2010 at 05:44:29PM +0000, abala...@users.sourceforge.net > > wrote: > > > I've just read yours bug report. But unfortunately, I couldn't reproduce > > > it (in Ubuntu > > > 10.10 with KDE and latest updates). Can you provide me some extra > > > information? Is > > > it new install (i.e. do you try to remove config files)? Do you have a > > > valgrind output or > > > some debug traces? > > > > I think it was upgraded (0.5.2 -> 0.6.3), but I'm not quite sure. I > > can try to remove the config files for udav. I wll report. Removing the config files for udav, causes the same. > > What further information would you find usefull? I can send as soon > > (probalby on monday) I can send you too the 'valgrind udav' output. > > Would you like to have some further information I can collect? > > Really I don't know -- I need to now which function cause the segfault. > May be "valgrind udav" will be enough (but, please, change "release" to > "debug" in src/src.pro to see the function names). Ok I have done this. Rebuilded and now I can provide you the log. It is attached to this mail. Do you see what could be wrong? Bests and thanks again Salvatore
udav.valgrind.log.gz
Description: Binary data
signature.asc
Description: Digital signature
