pidgin crashed with SIGSEGV in msn_cmdproc_process_cmd()

[Stéphane Loeuillet]

Binary package hint: pidgin

I was idle (Do not disturb)

only msn & gtalk account were active

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 12 17:22:52 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.1.0-1ubuntu2
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcCwd: /home/leroutier
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 msn_cmdproc_process_cmd (cmdproc=0xe6ce80,
 read_cb (data=0xe6cfa0,
 pidgin_io_invoke (source=<value optimized out>,
 IA__g_main_context_dispatch (context=0x6fb620)
 g_main_context_iterate (context=0x6fb620, block=1,
Title: pidgin crashed with SIGSEGV in msn_cmdproc_process_cmd()
Uname: Linux portable-sloeuillet 2.6.22-9-generic #1 SMP Fri Aug 3 00:20:35 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev pulse-rt scanner video
SegvAnalysis:
 Segfault happened at: 0x2b01adb0a9cd <nln_cmd+189>: mov %eax,0x4c(%rbx)
 PC (0x2b01adb0a9cd) ok
 source "%eax" ok
 destination "0x4c(%rbx)" (0x0000004c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

[Apport retracing service (apport)]

StacktraceTop:msn_cmdproc_process_cmd (cmdproc=0xe6ce80, cmd=0xfc9d80) at ../../../../libpurple/protocols/msn/cmdproc.c:313
read_cb (data=0xe6cfa0, source=<value optimized out>, cond=<value optimized out>) at ../../../../libpurple/protocols/msn/servconn.c:446
pidgin_io_invoke (source=<value optimized out>, condition=<value optimized out>, data=<value optimized out>) at ../../pidgin/gtkeventloop.c:77
IA__g_main_context_dispatch (context=0x6fb620) at /build/buildd/glib2.0-2.13.7/glib/gmain.c:2061
g_main_context_iterate (context=0x6fb620, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.13.7/glib/gmain.c:2694

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Have you been able to reproduce this with an up to date Ubuntu system ?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

[Gabriel Bauman (gabrielbauman)]

See #239300 for what appears to be the same bug on an up-to-date system.

[Rolf Leggewie (r0lf)]

resolved as dupe of 239300 which itself is a dupe of 214635