[GnomeMeeting-devel-list] Re: How to debug such a problem quickly

["Damien Sandras" <dsandras seconix com>]

Easy.

I have done a routine that will translate your group names if they are
translated when you upgrade.

But I forgot one case that puzzles GConf, the case where it is not
translated. It is thus trying to rename itself!

Just edit ldap_window.cpp, line 3762, and replace :

if (!contact_section_old || !contact_section_new)
return;

by

/* Do nothing if no contact section is specified or if they are
 * identical
 */
if (!contact_section_old || !contact_section_new || !strcmp
(contact_section_new, contact_section_old)
return;


If it works, just commit. It works in french because I updated the french
translation for my tests.

THANKS for noticing that HUGE bug!



Le 10/2/2004, "Kilian Krause" <kk verfaction de> a écrit:

>Hi Damien,
>
>Am Di, den 10.02.2004 schrieb Damien Sandras um 10:18:
>> Hi Kilian
>> 
>> Here is a quick howto to help determining such a problem.
>> 
>> You see in main_window.cpp that there is the main () method.
>> That is the start of gnomemeeting.
>> 
>> So you can do :
>> 'gdb gnomemeting'
>> 'break main_window.cpp:1562'
>> 
>> That means that the program will stop at the very beginning before
>> gnome_program_init.
>> 
>> 'run'
>> 
>> When it breaks on line 1562, you type:
>> 'next'
>> 
>> then you can type on the RETURN key until it loops, it will repeast the
>> 'next' instruction for you.
>
>it leaves off at:
>1599    in main_window.cpp
>(gdb) n
>-----------------(shaddering HD)---------------
>
>> Once you see where it loops, you can mail me and I'll help u further.
>> You will get the mechanism rapidly I think.
>
>-- 
>Best regards,
> Kilian