Gaim crash while chating

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

I have started the Gaim using Valgrind as suggested in the link https://wiki.ubuntu.com/Valgrind

Gaim exited very soon now. I am not sure that this is the same crash... Anyway, I got the bug log.

Just one question: is this the last log I must get for this crash? Is not there any other debugger software log you could ever need? That could save a lot of time in subsequent bugs.

Thank you

Another segmentation fault. Probably the same.

Cheers

One of the problem indicated by the log:

==5181== Invalid read of size 1
==5181== at 0x40221EB: strcmp (mc_replace_strmem.c:340)
==5181== by 0x57690AA: msn_session_find_slplink (slplink.c:138)
==5181== by 0x57692EB: msn_session_get_slplink (slplink.c:150)
==5181== by 0x5766C18: msn_emoticon_msg (slp.c:825)
==5181== by 0x5756622: msn_cmdproc_process_msg (cmdproc.c:248)
==5181== by 0x576AD73: msg_cmd_post (switchboard.c:734)
==5181== by 0x57566DC: msn_cmdproc_process_payload (cmdproc.c:223)
==5181== by 0x5765927: read_cb (servconn.c:433)
==5181== by 0x80FAFE2: gaim_gtk_io_invoke (gtkeventloop.c:74)

what version of gaim do you use?

El dom, 11-02-2007 a las 16:12 +0000, Sebastien Bacher escribió:
> what version of gaim do you use?
>

I use gaim v2.0.0beta3.1

Should I use another version? In that case, could you tell me please
where I may get it?

feisty has 2.0beta6, no point to update for it though. I'll probably build a package for edgy later. What architecture do you use?

I use a Centrino... Intel architecture.

El lun, 12-02-2007 a las 15:16 +0000, Sebastien Bacher escribió:
> feisty has 2.0beta6, no point to update for it though. I'll probably
> build a package for edgy later. What architecture do you use?
>

RIOU, thank you for your contribution. Your bug is not the same problem than the one you are commenting one though which creates confusion and gives extra work to people working to triage and fix bugs. If you are not sure of what you are doing could you open a new bug rather than commenting on random bug? Your problem is bug #72204

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.