[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [kopete-devel] Review Request: Implements mail notification and
From:       Gustavo Boiko <gustavo.boiko () kdemail ! net>
Date:       2009-07-17 17:29:06
Message-ID: 74A341CA-092C-42F7-A840-8EA14E146680 () kdemail ! net
[Download RAW message or body]

Hi

Em 17/07/2009, ās 14:20, Lamarque Vieira Souza escreveu:

> Em Sexta-feira 17 Julho 2009, Gustavo Boiko escreveu:
>> Hi
(...)
>>
>> It is usually a better approach to analyze the backtrace of the crash
>> than to start blindly setting pointers to zero after deletion. I'm  
>> not
>> saying pointers shouldn't be resetted after deleting, but usually
>> fixing a crash involves more than just doing that.
>
> 	For a particular case you are right. I did a mistake in not  
> nullifing deleted
> pointers in my open inbox implementation, that caused a crash with  
> backtrace.
> I thought that could be happening in other parts of Kopete source  
> code so I
> started to analise them all. Sorry if that was a waste of your time.  
> For me it
> was a good lesson on how to use delete and nullifing in C++ (I more  
> used to C
> than C++).

I didn't say it was a waste of time. In fact it was more a suggestion  
of a better way to face and fix crashes.

It is nice to know you learned by doing this. If you need help on  
debugging kopete or any other KDE application, I will be glad to help,  
just drop by in #kopete on irc.freenode.net or private mail me. There  
is no problem about.

In fact if you choose to private mail me, you can even write in  
portuguese (as we speak the same language).

Cheers

Boiko
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

[prev in list] [next in list] [prev in thread] [next in thread]